OAuth 2.0
OAuth 2.0 is an industry-standard authorization protocol that enables your client to securely delegate limited access to other clients without exposing sensitive credentials. Instead of you having to share passwords or API keys, OAuth 2.0 enables secure token-based authentication between clients for better security and control over data access. This guide explains the different OAuth 2.0 integration methods available through and how to integrate to the best method for your organization. For the purposes of this guide, a client can be an application, platform, system, or AI agent, depending on your organization.
Benefits
OAuth 2.0 replaces direct credential sharing with a secure-token method, which provides these benefits:
- Enables delegated access for merchants authorizing partner access.
- Supports system-to-system integrations without user interaction.
- Enables controlled access using scopes and tokens.
- Users can revoke access at any time.
Participants
OAuth 2.0 involves these participants working together to grant client access securely:
- Merchant: the resource owner who owns the protected resource and can grant your client access to it.
- OAuth API: the authorization server that authenticates the resource owner and issues access tokens after a successful authorization.
- APIs: the resource server that hosts the protected resource that you want to access, such as the payments API.
- Client or portfolio: the technology partner solution or acquirer platform that requests access to the protected resource on behalf of the resource owner.
Choose Your Integration Method
offers three OAuth 2.0 integration methods. The method you integrate to is determined by your organization type and how your client obtains consent from another organization to access their data.
Integration Methods
| Feature | On-Behalf-Of | Machine-to-Machine | OpenID Connect |
|---|---|---|---|
| Grant type | Authorization code grant | Client credentials grant | Authorization code grant |
| Consent | A merchant or user signs in and grants your client permission to act on their behalf | No user sign-in and no merchant consent during the flow | A user signs in through one of the supported sign-in methods |
| Available to | AI agent enablers, partner acquirers and partner resellers, technology partners, and merchants | AI agent enablers, merchants, partner acquirers and partner resellers, and technology partners | Partner acquirers and partner resellers, and technology partners |
On-Behalf-Of
The On-Behalf-Of (OBO) integration method uses the authorization code grant. A merchant or user signs in to the and grants your client permission to act on their behalf.
This table lists the organization types that can use the On-Behalf-Of integration method and a business example for each:
| Organization Type | Example |
|---|---|
| AI agent enabler | An AI assistant performs payment operations, dispute handling, or reconciliation on behalf of a consenting merchant, limited to the permissions that the merchant approves. |
| Partner acquirer or partner reseller | A bank portal initiates refunds or views reporting data on behalf of its merchants. |
| Technology partner | A SaaS platform accesses payment and reporting APIs on behalf of its merchants. |
| Merchant | A merchant grants a trusted client permission to access account data or perform permitted API operations on the merchant's behalf. |
Machine-to-Machine
The Machine-to-Machine (M2M) integration method uses the client credentials grant. Your system accesses APIs without user sign-in or merchant consent during the flow. The client and authenticate each other before issues an access token.
This table lists the organization types that can use the Machine-to-Machine integration method and a business example for each:
| Organization Type | Example |
|---|---|
| AI agent enabler | An AI coding agent or automated process connects to MCP to perform reconciliation, reporting, or scheduled payment operations. |
| Merchant | A merchant ERP or reconciliation system accesses payment APIs securely with OAuth tokens instead of static API keys. |
| Partner acquirer or partner reseller | An enterprise reporting platform or AI automation system aggregates data across multiple merchants. |
| Technology partner | A Remote MCP integration or embedded component calls APIs as a system client. |
OpenID Connect
The OpenID Connect (OIDC) integration method uses the authorization code grant. Your client authenticates users with one of the supported sign-in methods:
- Sign in through the .
- Single sign-on, or SSO.
- A federated identity relationship between and another platform.
This table lists the organization types that can use the OpenID Connect integration method and a business example for each:
| Organization Type | Example |
|---|---|
| Partner acquirer or partner reseller | A bank platform uses federated login with or coordinates sign-in across multiple merchants. |
| Technology partner | A partner portal uses SSO so merchants can sign in with their credentials. |
Thanks for your feedback!
Last published: November 18, 2026