Navigate to Applications.

Switch Development Client Keys with Production Client Keys🔗

Razorpay creates an application that appears on the list of created applications. The Edit Application page shows the application settings for both Development and Production clients. Client ID and Client Secret are predefined for both Development and Production clients. Use them to make request calls to Razorpay servers.

quest

Edit the Redirect URIs for your clients if needed. Click Save.

Given below is a comparison of the development and production clients:

Applications are external entities visible to the user. Internally, however, Razorpay OAuth works with clients identified by their client_id. When you create an application on Razorpay, we generate two clients linked to the application - development and production clients. Each client has its own client_id and client_secret. You can use the development client in your sandbox environment or during the integration phase, and the production client once you go live.

will redirect

Merchant

Mercha

platform partner

You should have the following ready:

completing

authenticate

has to

OAuth or Open Authorisation

You can

,

then

s

simply

linked account

:

:

You can use the following endpoint

linked account

Transfers are settled as per the settlement_period defined for the accoun

You have complete control over settlements to linked accounts.

automate reversals

Partial reversals are also supported, and you can create multiple reversals on a transfer_id. If you do not provide the amount parameter in the request, then the entire amount of the transfer is reversed.

This request creates a reversal entity and reverses the funds transferred from your account.

You can use the following endpoint to creat

When refunding a payment that has transfers, the amount is deducted from your main account balance. You can set the reverse_all parameter to 1 in the refund POST request to recover the amount from the linked account. This process will recover the amount from the linked account for every transfer made on the payment before processing the refund to the customer.

Refunds API

You can use the following endpoint to fetch

transfer

You should append ?expand[]=recipient_settlement as the query parameter to the fetch transfer request. This would return a settlement entity and the transfer entity.

the following endpoint to fe

You can use the following endpoint to

You can use the following endpoint to fetch

Use this endpoint to fetch

transfer

The response parameters are same as the transfer entity parameters.

Use this

will be

will be

Below are the possible values:

linked account:

Transfer funds to multiple Linked Accounts. Refund payments and reversal transfers from a Linked Account. Manage settlements and reconciliations. Hold settlements for Transfers.

Using Route APIs, you can:

Use Case🔗

Know more about Route before proceeding with the below APIs.

will be

Primary Details Bank Details Linked Account Name Type Contact Number Account Number

You can transfer funds to a vendor by creating a Linked Account using the Razorpay Dashboard.

Razorpay Route enables you

rieve details for a specific or multiple refund(s) using the unique identifier linked to the payment.

handy

s:

additional nominal

ou can retrieve details of a customer using the unique identifier (ID) linked to the customer. Use the following endpoint for the same.

You can retrieve details related to all customers using the Fetch all Customers API. Use the following endpoint for the same.

You can edit the customer details such as name, email and contact details using Edit Customer Details API. Use the following endpoint for the same.

You can create or add a customer using Create a Customer API with basic details such as name and contact details. You can use this API for various Razorpay Solution offerings. Use the following endpoint for the same.

Add or create a customer by providing basic details such as name, email and contact information to use them for the various Razorpay solutions. Edit the existing customer details. Retrieve information about all customers. Retrieve details for a specific customer using the unique identifier linked to the customer.

Razorpay Customers enables you to add or create customers with basic details such as name, email and contact details. You can then offer various Razorpay solutions to your customers. It also allows editing the customer details.

Notes can be used to record additional information about the payment. You can add up to 15 key-value pairs with each value of the key not exceeding 256 characters.

Note:

Refund will be processed at an optimal speed based on Razorpay's internal fund transfer logic. If the refund can be processed instantly, Razorpay will do so, irrespective of the payment method used to make the payment. If an instant refund is not possible, Razorpay will initiate a normal refund.

For information about the platform fees and different payment methods that support Instant Refunds, refer to the product documentation.

While issuing refunds, you can choose to process the refunds instantly or at normal speed (within 5-7 working days).

ays).

a

That is,

This mean

That is:

That is:

That is,

with

Here is

Razorpay provides you real-time tracking of the processing speed and the status of the initiated refund.

Watch Out

You can view the st

as shown here:

then

merchant

as show

alert

Merchant

Raising request sends email to the sub-merchant to request access for performing KYC

counts section of your Partner Dashboard, click on Request for KYC under the Actions column for the merchant you want to perform KYC for. to send an email to the sub-merchant to request access for performing KYC.

for

Perform KYC

Know how to submit KYC documents for your sub-merchants.

Click Perform KYC for more information.

Dashboard.

erform KYC f

Generate Signature on your Server🔗

Poll APIs🔗

Example🔗

Subscribe to Webhook events

Verify Payment Status From Dashboard🔗

Server-to-server

Integrate the Payments Rainy Day Kit

Verify the Payment🔗

:

Server-to-server

Next Steps🔗

Integrate the Payments Rainy Day Kit🔗

(both collect and intent flows)

Request Parameters

Payment using Redirect🔗

OTP Submit🔗

Payment using Native OTP as Preferred Auth🔗

Payment using Native OTP with Redirect Fallback🔗

Payment using Native OTP🔗

The OTP Submit and Resend APIs will return a response in the same format given here.

:

Request Parameters

The following is a sample API request and response for creating an order:

would like greater control

The payment creation request returns a variety of responses, all of which need to render on your customer's browser to push the payment forward. These responses result in redirecting the browser to a bank or gateway page to complete payment authentication.

fairly

server-to-server integration i

there is no redirect involved when the customer completes the payment, you will have to poll the Razorpay APIs to get the latest status of the payment.

Generate Signature on your Server🔗

Failure Callback🔗

Success Callback

an Order🔗

Generate Signature on your Server🔗 Java PHP Ruby PythonCopy

Failure Callback🔗

Success Callback🔗

Request Parameters

The following is a sample API request and response for creating an order: Curl Java Python PHP .NET Ruby Node.JS Go ResponseCopy

Request Parameters

The following is a sample API request and response for creating an order:

Generate Signature on your Server🔗 Java PHP Ruby Python .NET NodeJS GoCopy

Response on OTP Submit🔗

Response Parameters

Path Parameter🔗

OTP Generation

Response Parameters🔗

Request Parameters🔗

OTP Submit🔗

Generate Signature on your Server

Response Parameters🔗

Request Parameters🔗

Request Parameters

The following is a sample API request and response for creating an order:

To begin processing a payment,

tegration

If you would like greater control over the manner in which the customer is redirected, you can choose to use the JSON API. That is, you can decide where the customer should enter the transaction OTP to complete the payment:

This is our default server-to-server integration. Here, the payment creation request returns a variety of responses which must be rendered on your customer's browser to proceed with the payment. These responses normally result in the browser being redirected to a bank or gateway page to complete payment authentication.

Feature Request This is an on-demand feature. Please raise a request with our Support team to get this feature activated on your Razorpay account.

Next Steps🔗

payment create request

Verify the Payment🔗

A sample of the request for creating the payment:

der is shown below:

To understand how Orders are implemented in Razorpay, refer Orders documentation.

PCI compliance

:

Familiarize yourselves with Razorpay payment flow to understand the payment life cycle.

If you don't have any, generate the the API keys from the Razorpay Dashboard.

Raise a request with our Support team to get this feature enabled on your account, as it is available only on request basis.

Server-to-server payments integration lets you communicate directly with the Razorpay servers and seamlessly integrate the service in your web application. The direct integration enables you to capture payment details on your own secure server and process the payments at your end, in preference to using our standard Checkout. This integration method provides you with complete control over the look and feel of the payment experience for your customers.

Integrate the Payments Rainy Day Kit🔗

The sample payloads for each of the payment methods can be used while creating a payment in the integration flow.

-

-

-

-

Pass the method and provider parameters in Create Payments API🔗

Default supported wallets are freecharge and payzapp.

Pass app_offer Parameter in Order🔗

be registered account holders of

Prerequisites🔗

You can enable your customers to make payments using the Pay Later service offered by various third-party providers such as:

For UPI payments, refer to the UPI Intent and UPI Collect documentation.

You can fetch the available EMI plans (for each supported bank) by invoking the Methods API. Extract the EMI plans from the response to be shown to your customers while making the payment. Know more about EMI plans offered by OneCard and HSBC.

,

To learn about errors, refer to the FAQ Upload the NACH File section.

Refer to the Recurring Payments Paper NACH documentation for the steps 1,2,4 and 5.

Upload the NACH File via API

Using create NACH file API, you can upload the signed NACH forms which are collected from your customers. Razorpay OCR-enabled NACH engine submits the form to NPCI on successful verification and you will receive a success/failure response.

Sample checkout code to collect the authorization transaction🔗

Read More: Refer to the Recurring Payments API documentation for more information about steps 2, 3, 4 and 5.

Using custom checkout. Using an authorization link.

For more information about authorization and subsequent payments, refer to the Recurring Payments documentation.

You can fetch the codes of the available banks from here.

fields🔗

:

Before constructing the payloads for each of the payment methods, familiarize yourselves with the fields required to construct a payment request.

To know the payment methods that are activated for your account, refer to this document.

Razorpay allows you to accept payments through a host of

Now that you know the available payment methods,

t.

We recommended using S2S JSON API for S2S integration. For redirect flow, you must open the HTML provided as part of the API response, as is from the customer's browser. You should pass the actual user_agent, customer IP and referrer to avoid any failures due to risk. You should integrate webhooks to get a callback via a server to server call. Integrate the Payments Rainy Day kit to tackle payment exceptions such as late authorized payments, payment downtimes and errors.

on the same

Razorpay S2S Integration - Best Practices