Payment-provider OAuth callback
Browser redirect target: the provider lands here after the user authorizes. Payssage exchanges the code, stores the provider credential, and redirects the browser to the `final_redirect_url` captured at connect time. Public — the provider's OAuth flow cannot send an Authorization header.
/providers/{provider}/callbackBrowser redirect target: the provider lands here after the user
authorizes. Payssage exchanges the code, stores the provider
credential, and redirects the browser to the final_redirect_url
captured at connect time. Public — the provider's OAuth flow
cannot send an Authorization header.
Path Parameters
Payment provider slug (e.g. mercadopago).
Query Parameters
Authorization code issued by the provider.
CSRF state issued at connect time.
Response Body
application/json
application/problem+json
curl -X GET "https://example.com/providers/string/callback?code=string&state=string""http://example.com"{
"detail": "string",
"instance": "../dictionary",
"errors": [
{
"field": "string",
"message": "string"
}
],
"type": "http://example.com",
"status": 400,
"title": "Validation Failed"
}Start a payment-provider OAuth connection POST
Starts an OAuth connection to the given payment provider (`mercadopago`). Callers must pass the flow (`collector` or `seller`) and the final redirect URL (where the user lands after the provider's consent screen). The provider redirect URI is Payssage's own callback (`/providers/{provider}/callback`), configured on the server (`MP_REDIRECT_URI`) — callers never supply one. The response carries the URL to send the user to.
Revoke a payment-provider connection POST
Revokes a connected provider credential (collector or seller).