If ever, do you have a list of common reasons for this, so we can prepare prompts for our application.
Common reasons for authorization failures in Maya’s OAuth 2.0 flow include:
- Invalid client credentials: The client_id or client_secret provided is incorrect, missing, or improperly encoded in the Authorization header.
- Missing grant_type: The request body does not include the required grant_type parameter (e.g., authorization_code or refresh_token).
- Unsupported grant_type: The grant_type specified is not allowed for your integration (e.g., using client_credentials when authorization_code is required).
- Invalid authorization code: The code received from the redirect URI has expired (valid for 300 seconds), has already been used, or is malformed.
- Invalid refresh token: The refresh token provided is expired, revoked, or incorrect.
- Locked user account: The end user’s Maya account has been locked due to too many failed login attempts.
- Mismatched redirect_uri: The redirect URI in the authorization request does not exactly match the one registered with Maya.
- Invalid scope or key scope: The API key or client does not have the required permissions or scope for the requested operation.
For Sandbox concerns and other technical implementation inquiries, please get in touch with us via:
- Sandbox Health Page: Check real-time service status updates.
- Maya Developer Hub Service Desk: File
a ticket in Sandbox.
To Know More:
We value your input and would love to hear your insights. Please submit you feedback here.
In addition to the response, you might find this resource helpful for a deeper understanding of the topic: Authentication and API Key Errors, if you are transacting an online payment in Maya.
Thanks!