: Custom fields specific to the type , such as amount , currency , or account_id . 2. Implementation Workflow
This feature enables clients to specify fine-grained authorization requirements, such as requesting access to specific bank accounts or certain transaction amounts, rather than using broad, pre-defined scopes. 1. Core Components
: Update the consent UI to parse the JSON authorization_details and display them in a human-readable format (e.g., "Allow app to pay $50.00 from Account X"). 4839005059204218ae8e0c51956c63d6.rar
: Ensure that authorization_details are treated with the same (or higher) level of validation as standard scopes.
: A string identifying the type of authorization (e.g., payment_initiation , account_information ). : Custom fields specific to the type ,
: A new JSON-based parameter used in authorization and token requests.
: Create a registry of authorization detail types your system supports. : A string identifying the type of authorization (e
To draft this feature properly, your implementation should follow these steps outlined in the IETF OAuth RAR Implementation Considerations: