Before you begin
OAuth applications live on the Razorpay Partner Dashboard, so the partner account has to
exist before there is anything to register.
- Become a Razorpay Technology Partner and complete partner KYC.
- Sign in to the Razorpay Dashboard with an Owner user.
- OAuth grants access to a sub-merchant’s Razorpay Payments data. The sub-merchant approves the request themselves and can revoke it at any time from their own dashboard.
Register the OAuth application
Razorpay issues the Client ID and Client Secret when the application is saved, and shows
them on the application’s settings page for both the development and production clients.
Open the Applications tab
In the Razorpay Dashboard, select Partner, then open Applications. The tab lists
every application already registered under Created Applications.
Create the application
Select Create Application and fill in the form.
- Name: the name shown to sub-merchants on Razorpay’s authorization screen, for example
StackOne Integration. - Website: the URL of your application’s website.
- Logo: upload a square image. Razorpay substitutes a default logo if you skip this.
- Select Save.
Add the redirect URI
The Edit Application page opens with separate Development and Production
client settings. Add the callback URL to the Redirect URIs field of the client you
intend to use.
- Redirect URIs: the Callback URL from your Connector Profile.
- Razorpay compares the redirect URI against its saved value exactly on both the authorization request and the token exchange, so copy it without changes.
- Multiple redirect URIs are entered comma-separated.
- The production client accepts HTTPS URIs only. The development client also accepts localhost and non-HTTP URIs.
- Select Save.
Copy the credentials
Client ID and Client Secret are shown on the same page, masked until you unmask
them, for the development and production clients separately.
- Copy the production client’s Client ID into your Connector Profile.
- Copy the production client’s Client Secret into your Connector Profile.
- Do not expose the Client Secret publicly - it authenticates your application on the server-to-server token exchange.
Access the connector requests
Razorpay’s Payments scopes are account-wide rather than per-resource, and the scope
travels on the authorization URL - there is nothing to select on the Partner Dashboard.
Review the access level
The sub-merchant sees the requested access on Razorpay’s consent screen and approves
it there.
read_writecovers every action in this connector - the reads plus create, update, capture and cancel.read_onlycovers the read actions alone, and Razorpay refuses the write ones.- Razorpay takes a single scope value on the authorization URL; multiple scopes need array notation, which this connector does not send.
- Razorpay also defines RazorpayX scopes (
rx_read_only,rx_read_write,rx_partner_read_write) for banking resources. This connector maps no RazorpayX endpoints, so those scopes grant it nothing.
Create the StackOne Connector Profile
Create a Connector Profile
Link an Account