---
title: "Rich Authorization Requests (RFC 9396): definition | KYA glossary"
url: https://knowyouragent.ch/en/knowledge/glossary/rich-authorization-requests
lang: en
updated: 2026-10-12
license: © Innopulse Consulting GmbH
---

# Rich Authorization Requests (RFC 9396)

Rich Authorization Requests (RAR) are an OAuth extension defined in RFC 9396 that lets a client request fine-grained permissions as structured details instead of plain scopes.

Classic OAuth scopes such as “payments” say little about which payment is allowed. RFC 9396, published in May 2023, introduces the authorization_details parameter for this: a JSON array in which each entry holds a type and the concrete details, such as amount, currency, payee or account. The authorization server shows these details to the user for consent and carries them into the issued token.

For AI agents, RAR is the obvious way to fix the limits of a single action at the point of access. The details remain part of an access token, however; on their own, they say nothing about the time of the action, its execution or revocation.

## Example

An agent wants to pay an invoice of CHF 480 to a specific supplier. It requests a token with authorization_details: type “payment_initiation”, amount CHF 480, payee with IBAN. The user confirms exactly this payment, and the bank executes only that one.

## How it differs

A scope allows a category; RAR allows a concretely described action. An [agent mandate](https://knowyouragent.ch/en/knowledge/glossary/agent-mandate) goes further: it applies across several actions, names [principal](https://knowyouragent.ch/en/knowledge/glossary/principal) and agent, can be revoked through a [status list](https://knowyouragent.ch/en/knowledge/glossary/status-list) and, with decision and receipt, becomes verifiable evidence.

## In practice

- Describe the concrete limits in authorization_details, not just the type: amount, currency, payee and validity.
- Show the user the details in readable form at consent, so she knows what she allows.
- Also record the permission granted as signed evidence, so it stays verifiable outside the authorization server.

## Role in KYA

KYA does not verify OAuth tokens, but it asks the same question at the level of evidence: was the action within scope? Whoever uses RAR can carry the authorization_details into a mandate and so make the same limits independently verifiable.

Related check: [Scope of the action](https://knowyouragent.ch/en/method/checks) (`intent_scope`). Is the action within the mandate's action type, amount limit, currency and counterparty?

[Verify now: open a matching example](https://knowyouragent.ch/en/verify?beispiel=abgelehnt)

## Frequently asked questions

### What is the difference between RAR and OAuth scopes?

Scopes are plain strings for categories such as “read” or “pay”. RAR describes a permission as a structured object with concrete details, such as the amount and payee of a payment.

### Where is RAR used?

Mainly in payments and open banking, where individual payments or account access must be described and confirmed precisely. For AI agents, RAR is interesting because it fixes the limits of an action early.

### Does RAR replace an agent mandate?

No. RAR governs access to an interface. A mandate describes the instruction across several actions, can be revoked and, with decision and receipt, becomes evidence that third parties can verify.

### Can KYA verify authorization_details?

KYA does not verify OAuth tokens. The limits from authorization_details can, however, be carried into a mandate; KYA then checks whether the action stayed within that scope.

## Sources

- [RFC 9396: OAuth 2.0 Rich Authorization Requests](https://www.rfc-editor.org/rfc/rfc9396)

## Related terms

- [Agent mandate](https://knowyouragent.ch/en/knowledge/glossary/agent-mandate)
- [Least privilege](https://knowyouragent.ch/en/knowledge/glossary/least-privilege)
- [OAuth Token Exchange (RFC 8693)](https://knowyouragent.ch/en/knowledge/glossary/token-exchange)
- [Model Context Protocol (MCP)](https://knowyouragent.ch/en/knowledge/glossary/mcp)

---
Quelle: https://knowyouragent.ch/en/knowledge/glossary/rich-authorization-requests · KYA – Know Your Agent