Standard Checkout - Integration Steps

Follow these steps to integrate the Standard Checkout form on your website:

Before You BeginEnsure your account is ready for integration:

Your Razorpay account is activated (required for Live mode).
You have generated API keys for the correct mode (Test or Live).
Test mode API keys start with rzp_test_ and Live mode keys start with rzp_live_.
Your website domain is whitelisted in the Dashboard.

1. Build Integration

Integrate Web Standard Checkout.

2. Test Integration

Test the integration by making a test payment.

3. Go-live Checklist

Check the go-live checklist.

1. Build Integration

Follow the steps given below:

1.1 Create an Order in Server

Given below are the order states and the corresponding payment states:

Payment Stages	Order State	Payment State	Description
Stage I	created	created	The customer submits the payment information, which is sent to Razorpay. The payment is not processed at this stage.
Stage II	attempted	authorized/failed	An order moves from created to attempted state when payment is first attempted. It remains in this state until a payment associated with the order is captured.
Stage III	paid	captured	After the payment moves to the captured state, the order moves to the paid state. No more payment requests are allowed after an order moves to the paid state. The order continues to be in this state even if the payment for this order is refunded.

Capture Payments AutomaticallyYou can capture payments automatically with the one-time Payment Capture setting configuration on the Dashboard.

Order is an important step in the payment process.

An order should be created for every payment.
You can create an order using the Orders API. It is a server-side API call. Know how to authenticate Orders API.
The order_id received in the response should be passed to the checkout. This ties the order with the payment and secures the request from being tampered.

Watch Out!Payments made without an order_id cannot be captured and will be automatically refunded. You must create an order before initiating payments to ensure proper payment processing.

Use the below endpoint to create an order in your (backend) server.POST /orders

curl -X POST https://api.razorpay.com/v1/orders \
-U [YOUR_KEY_ID]:[YOUR_KEY_SECRET] \
-H 'content-type:application/json' \
-d '{
    "amount": 50000,
    "currency": "INR",
    "receipt": "qwsaq1",
    "partial_payment": true,
    "first_payment_min_amount": 230
}'

RazorpayClient razorpay = new RazorpayClient("[YOUR_KEY_ID]", "[YOUR_KEY_SECRET]");

JSONObject orderRequest = new JSONObject();
orderRequest.put("amount", 50000); // amount in the smallest currency unit
orderRequest.put("currency", "INR");
orderRequest.put("receipt", "order_rcptid_11");

Order order = razorpay.Orders.create(orderRequest);
} catch (RazorpayException e) {
// Handle Exception
System.out.println(e.getMessage());
}

import razorpay
client = razorpay.Client(auth=("YOUR_ID", "YOUR_SECRET"))

DATA = {
    "amount": 50000,
    "currency": "INR",
    "receipt": "receipt#1",
    "notes": {
        "key1": "value3",
        "key2": "value2"
    }
}
client.order.create(data=DATA)

$api = new Api($key_id, $secret);

$api->order->create(array('receipt' => '123', 'amount' => 50000, 'currency' => 'INR', 'notes'=> array('key1'=> 'value3','key2'=> 'value2')));

RazorpayClient client = new RazorpayClient(your_key_id, your_secret);

Dictionary options = new Dictionary();
options.Add("amount", 50000); // amount in the smallest currency unit
options.add("receipt", "order_rcptid_11");
options.add("currency", "INR");
Order order = client.Order.Create(options);

require "razorpay"
Razorpay.setup('YOUR_KEY_ID', 'YOUR_SECRET')

options = amount: 50000, currency: 'INR', receipt: ''
order = Razorpay::Order.create

var instance = new Razorpay({ key_id: 'YOUR_KEY_ID', key_secret: 'YOUR_SECRET' })

instance.orders.create({
amount: 50000,
currency: "INR",
receipt: "receipt#1",
notes: {
    key1: "value3",
    key2: "value2"
}
})

import ( razorpay "github.com/razorpay/razorpay-go" )
client := razorpay.NewClient("YOUR_KEY_ID", "YOUR_SECRET")

data := map[string]interface{}{
"amount": 50000,
"currency": "INR",
"receipt": "some_receipt_id"
}
body, err := client.Order.Create(data)

Success Response
Failure Response

{
    "id": "order_IluGWxBm9U8zJ8",
    "entity": "order",
    "amount": 50000,
    "amount_paid": 0,
    "amount_due": 50000,
    "currency": "INR",
    "receipt": "rcptid_11",
    "offer_id": null,
    "status": "created",
    "attempts": 0,
    "notes": [],
    "created_at": 1642662092
}

{
  "error": {
      "code": "BAD_REQUEST_ERROR",
      "description": "Order amount less than minimum amount allowed",
      "source": "business",
      "step": "payment_initiation",
      "reason": "input_validation_failed",
      "metadata": {},
      "field": "amount"
  }
}

An order id (referred as order_id) is generated on the successful creation of an order. You should store this order id in your system against the order.Know more about Orders API.

Handy TipsUnder the Authorization section in Postman, select Basic Auth and add the Key Id and secret as the Username and Password, respectively.

Request Parameters

integer

required

The transaction amount, expressed in the currency subunit. For example, for an actual amount of ₹222.25, the value of this field should be 22225.

string

required

The currency in which the transaction should be made. See the list of supported currencies. Length must be of 3 characters.

string

Your receipt id for this order should be passed here. Maximum length is 40 characters.

object

Key-value pair that can be used to store additional information about the entity. Maximum 15 key-value pairs, 256 characters (maximum) each. For example, "note_key": "Beam me up Scotty".

boolean

Indicates whether the customer can make a partial payment. Possible values:

true: The customer can make partial payments.
false (default): The customer cannot make partial payments.

integer

Minimum amount that must be paid by the customer as the first partial payment. For example, if an amount of ₹7,000 is to be received from the customer in two installments of #1 - ₹5,000, #2 - ₹2,000, then you can set this value as 500000. This parameter should be passed only if partial_payment is true.

Response Parameters

Descriptions for the response parameters are present in the Orders Entity parameters table.

Error Response Parameters

The error response parameters are available in the API Reference Guide.

1.2 Integrate with Checkout on Client-Side

Add the Pay button on your web page using the checkout code. You can use the handler function or callback URL.

1.2.1 Handler Function or Callback URL

Handler Function	Callback URL
When you use this: On successful payment, the customer is shown your web page. On failure, the customer is notified of the failure and asked to retry the payment.	When you use this: On successful payment, the customer is redirected to the specified URL, for example, a payment success page. On failure, the customer is asked to retry the payment.

1.2.2 Code to Add Pay Button

Copy-paste the parameters as options in your code:

Callback URL (JS)
Handler Functions (JS)

<button id="rzp-button1">Pay</button>
<script src="https://checkout.razorpay.com/v1/checkout.js"></script>
<script>
var options = {
    "key": "YOUR_KEY_ID", // Enter the Key ID generated from the Dashboard
    "amount": "50000", // Amount is in currency subunits. 
    "currency": "INR",
    "name": "Acme Corp", //your business name
    "description": "Test Transaction",
    "image": "https://example.com/your_logo",
    "order_id": "order_9A33XWu170gUtm", // This is a sample Order ID. Pass the `id` obtained in the response of Step 1
    "callback_url": "https://eneqd3r9zrjok.x.pipedream.net/",
    "prefill": { //We recommend using the prefill parameter to auto-fill customer's contact information especially their phone number
        "name": "Gaurav Kumar", //your customer's name
        "email": "gaurav.kumar@example.com",
        "contact": "+919876543210" //Provide the customer's phone number for better conversion rates 
    },
    "notes": {
        "address": "Razorpay Corporate Office"
    },
    "theme": {
        "color": "#3399cc"
    }
};
var rzp1 = new Razorpay(options);
document.getElementById('rzp-button1').onclick = function(e){
    rzp1.open();
    e.preventDefault();
}
</script>

<button id="rzp-button1">Pay</button>
<script src="https://checkout.razorpay.com/v1/checkout.js"></script>
<script>
var options = {
    "key": "YOUR_KEY_ID", // Enter the Key ID generated from the Dashboard
    "amount": "50000", // Amount is in currency subunits.
    "currency": "INR",
    "name": "Acme Corp", //your business name
    "description": "Test Transaction",
    "image": "https://example.com/your_logo",
    "order_id": "order_9A33XWu170gUtm", //This is a sample Order ID. Pass the `id` obtained in the response of Step 1
    "handler": function (response){
        alert(response.razorpay_payment_id);
        alert(response.razorpay_order_id);
        alert(response.razorpay_signature)
    },
    "prefill": { //We recommend using the prefill parameter to auto-fill customer's contact information, especially their phone number
        "name": "Gaurav Kumar", //your customer's name
        "email": "gaurav.kumar@example.com", 
        "contact": "+919876543210"  //Provide the customer's phone number for better conversion rates 
    },
    "notes": {
        "address": "Razorpay Corporate Office"
    },
    "theme": {
        "color": "#3399cc"
    }
};
var rzp1 = new Razorpay(options);
rzp1.on('payment.failed', function (response){
        alert(response.error.code);
        alert(response.error.description);
        alert(response.error.source);
        alert(response.error.step);
        alert(response.error.reason);
        alert(response.error.metadata.order_id);
        alert(response.error.metadata.payment_id);
});
document.getElementById('rzp-button1').onclick = function(e){
    rzp1.open();
    e.preventDefault();
}
</script>

Handy TipsTest your integration using these test cards.

1.2.3 Checkout Options

string

required

API Key ID generated from the Dashboard.

integer

required

Payment amount in the smallest currency subunit. For example, if the amount to be charged is ₹2222.50, enter 222250 in this field. In the case of three decimal currencies, such as KWD, BHD and OMR, to accept a payment of 295.991, pass the value as 295990. And in the case of zero decimal currencies such as JPY, to accept a payment of 295, pass the value as 295.

Watch Out!As per payment guidelines, you should pass the last decimal number as 0 for three decimal currency payments. For example, if you want to charge a customer 99.991 KD for a transaction, you should pass the value for the amount parameter as 99990 and not 99991.

string

required

The currency in which the payment should be made by the customer. See the list of supported currencies.

Handy TipsRazorpay has added support for zero decimal currencies, such as JPY, and three decimal currencies, such as KWD, BHD, and OMR, allowing businesses to accept international payments in these currencies. Know more about Currency Conversion.

string

required

Your Business/Enterprise name shown on the Checkout form. For example, Acme Corp.

string

Description of the purchase item shown on the Checkout form. It should start with an alphanumeric character.

string

Link to an image (usually your business logo) shown on the Checkout form. Can also be a base64 string if you are not loading the image from a network.

string

required

Order ID generated via Orders API.

object

You can prefill the following details at Checkout.

Boost Conversions and Minimise Drop-offs

Autofill customer contact details, especially phone number to ease form completion. Include customer’s phone number in the contact parameter of the JSON request’s prefill object. Format: +(country code)(phone number). Example: “contact”: “+919000090000”.
This is not applicable if you do not collect customer contact details on your website before checkout, have Shopify stores or use any of the no-code apps.

name (optional): Cardholder’s name to be prefilled if customer is to make card payments on Checkout. For example, Gaurav Kumar.
email (optional): Email address of the customer.
contact (optional): Phone number of the customer. The expected format of the phone number is + {country code}{phone number}. If the country code is not specified, 91 will be used as the default value. This is particularly important while prefilling contact of customers with phone numbers issued outside India. Examples: +14155552671 (a valid non-Indian number), +919977665544 (a valid Indian number). If 9977665544 is entered, +91 is added to it as +919977665544.
method (optional): Pre-selection of the payment method for the customer. Will only work if contact and email are also prefilled. Possible values: card, netbanking, wallet, upi, emi.

object

Set of key-value pairs that can be used to store additional information about the payment. It can hold a maximum of 15 key-value pairs, each 256 characters long (maximum).

object

Thematic options to modify the appearance of Checkout.

color (optional): Enter your brand colour’s HEX code to alter the text, payment method icons and CTA (call-to-action) button colour of the Checkout form.
backdrop_color (optional): Enter a HEX code to change the Checkout’s backdrop colour.

Options to handle the Checkout modal.

backdropclose (optional): Indicates whether clicking the translucent blank space outside the Checkout form should close the form. Possible values: true (Closes the form when your customer clicks outside), false (default - Does not close the form).
escape (optional): Indicates whether pressing the escape key should close the Checkout form. Possible values: true (default - Closes the form), false (Does not close the form).
handleback (optional): Determines whether Checkout must behave similar to the browser when back button is pressed. Possible values: true (default - Checkout behaves similarly to the browser), false (Checkout does not simulate a back press).
confirm_close (optional): Determines whether a confirmation dialog box should be shown if customers attempts to close Checkout. Possible values: true (Confirmation dialog box is shown), false (default - No confirmation dialog).
ondismiss (optional): Used to track the status of Checkout. You can pass a modal object with ondismiss: function(){} as options. This function is called when the modal is closed by the user.
animation (optional): Shows an animation before loading of Checkout. Possible values: true (default - Animation appears), false (Animation does not appear).

string

If you are accepting recurring payments using Razorpay Checkout, you should pass the relevant subscription_id to the Checkout. Know more about Subscriptions on Checkout.

boolean

Permit or restrict customer from changing the card linked to the subscription. Possible values: true (Allow the customer to change the card), false (default - Do not allow).

boolean

Determines if you are accepting recurring (charge-at-will) payments on Checkout via instruments such as emandate, paper NACH and so on. Possible values: true (Accepting recurring payments), false (default - Not accepting recurring payments).

string

Customers will be redirected to this URL on successful payment. Ensure that the domain of the Callback URL is allowlisted.

boolean

Determines whether to post a response to the event handler post payment completion or redirect to Callback URL. callback_url must be passed while using this parameter. Possible values: true (Customer is redirected to the specified callback URL in case of payment failure), false (default - Customer is shown the Checkout popup to retry the payment).

string

Unique identifier of customer. Used for:

Local saved cards feature.
Static bank account details on Checkout in case of Bank Transfer payment method.

boolean

Determines whether to allow saving of cards. Can also be configured via the Dashboard. Possible values: true (Enables card saving feature), false (default - Disables card saving feature).

integer

Sets a timeout on Checkout, in seconds. After the specified time limit, the customer will not be able to use Checkout.

Watch Out!Some browsers may pause JavaScript timers when the user switches tabs, especially in power saver mode. This can cause the checkout session to stay active beyond the set timeout duration.

object

Marks fields as read-only.

contact (optional): Used to set the contact field as readonly. Possible values: true (Customer will not be able to edit this field), false (default - Customer can edit).
email (optional): Used to set the email field as readonly. Possible values: true (Customer will not be able to edit this field), false (default - Customer can edit).
name (optional): Used to set the name field as readonly. Possible values: true (Customer will not be able to edit this field), false (default - Customer can edit).

object

Hides the contact details.

contact (optional): Used to set the contact field as optional. Possible values: true (Customer will not be able to view this field), false (default - Customer can view).
email (optional): Used to set the email field as optional. Possible values: true (Customer will not be able to view this field), false (default - Customer can view).

boolean

Used to auto-read OTP for cards and netbanking pages. Applicable from Android SDK version 1.5.9 and above. Possible values: true (OTP is auto-read), false (default - OTP is not auto-read).

boolean

Used to rotate payment page as per screen orientation. Applicable from Android SDK version 1.6.4 and above. Possible values: true (Payment page can be rotated), false (default - Payment page cannot be rotated).

object

Parameters that enable retry of payment on the checkout.

enabled: Determines whether the customers can retry payments on the checkout. Possible values: true (default - Enables customers to retry payments), false (Disables customers from retrying the payment).
max_count: The number of times the customer can retry the payment. We recommend you to set this to 4. Having a larger number here can cause loops to occur.

Watch Out!Web Integration does not support the max_count parameter. It is applicable only in Android and iOS SDKs.

object

Parameters that enable checkout configuration. Know more about how to configure payment methods on Razorpay standard checkout.

display: Child parameter that enables configuration of checkout display language.
- language: The language in which checkout should be displayed. Possible values: en (English), ben (Bengali), hi (Hindi), mar (Marathi), guj (Gujarati), tam (Tamil), tel (Telugu).

Handy TipsThe open method of Razorpay object (rzp1.open()) must be invoked by your site’s JavaScript, which may or may not be a user-driven action such as a click.

1.2.4 Errors

Given below is a list of errors you may face while integrating with checkout on the client-side.

Error	Cause	Solution
The id provided does not exist.	Occurs when there is a mismatch between the API keys used while creating the `order_id`/`customer_id` and the API key passed in the checkout.	Make sure that the API keys passed in the checkout are the same as the API keys used while creating the `order_id`/`customer_id`. For example, if the order was created using Test mode keys, use Test mode keys in the checkout.
Blocked by CORS policy.	Occurs when the server-to-server request is hit from the front end instead.	Make sure that the API calls are made from the server side and not the client side. The Orders API must be called from your backend server.
Payment blocked as website does not match registered website(s).	The domain from which checkout is loaded is not whitelisted.	Add your website URL to the whitelisted domains in Dashboard → Account & Settings → Website and app settings.
Access Denied (from gateway).	API keys are incorrect or your account has restrictions.	Verify you are using the correct API keys for the mode (Test/Live). Regenerate keys if needed. Check if your account is activated for Live mode.
Payment was not completed on time.	Customer did not complete payment within the timeout period (3-15 minutes).	This is expected behavior. The customer can retry the payment.

Payments Auto-Refunded?If customer payments are being automatically refunded, ensure you are passing a valid order_id in the checkout options. Payments made without an order_id cannot be captured and are automatically refunded. Always create an order before initiating checkout.

1.2.5 Configure Payment Methods (Optional)

Multiple payment methods are available on the Razorpay Web Standard Checkout.

The payment methods are fixed and cannot be changed.
You can configure the order or make certain payment methods prominent. Know more about configuring payment methods.

1.3 Handle Payment Success and Failure

The way the Payment Success and Failure scenarios are handled depends on the Checkout Sample Code you used in the last step.

Checkout with Handler Function

If you used the sample code with the handler function:

Payment Success
Payment Failure

On Payment SuccessThe customer sees your website page. The checkout returns the response object of the successful payment (razorpay_payment_id, razorpay_order_id and razorpay_signature). Collect these and send them to your server.

On Payment FailureThe customer is notified about payment failure and asked to retry the payment. Know about the error parameters.

rzp1.on('payment.failed', function (response){
    alert(response.error.code);
    alert(response.error.description);
    alert(response.error.source);
    alert(response.error.step);
    alert(response.error.reason);
    alert(response.error.metadata.order_id);
    alert(response.error.metadata.payment_id);
});

Checkout with Callback URL

If you used the sample code with the callback URL:

Payment Success
Payment Failure

On Payment SuccessRazorpay makes a POST call to the callback URL with the razorpay_payment_id, razorpay_order_id and razorpay_signature in the response object of the successful payment. Only successful authorisations are auto-submitted.

1.4 Store Fields in Your Server

A successful payment returns the following fields to the Checkout form.

You need to store these fields in your server.
You can confirm the authenticity of these details by verifying the signature in the next step.

{
  "razorpay_payment_id": "pay_29QQoUBi66xm2f",
  "razorpay_order_id": "order_9A33XWu170gUtm",
  "razorpay_signature": "9ef4dffbfd84f1318f6739a3ce19f9d85851857ae648f114332d8401e0949a3d"
}

Parameter	Description
`razorpay_payment_id`	Unique identifier for the payment returned by Checkout only for successful payments.
`razorpay_order_id`	Unique identifier for the order returned by Checkout.
`razorpay_signature`	Signature returned by the Checkout. This is used to verify the payment.

1.5 Verify Payment Signature

This is a mandatory step to confirm the authenticity of the details returned to the Checkout form for successful payments.To verify the razorpay_signature returned to you by the Checkout form:

Create a signature in your server using the following attributes:
- order_id: Retrieve the order_id from your server. Do not use the razorpay_order_id returned by Checkout.
- razorpay_payment_id: Returned by Checkout.
- key_secret: Available in your server. The key_secret that was generated from the Dashboard.

Use the SHA256 algorithm, the razorpay_payment_id and the order_id to construct a HMAC hex digest as shown below:

generated_signature = hmac_sha256(order_id + "|" + razorpay_payment_id, secret);

if (generated_signature == razorpay_signature) {
  payment is successful
}

If the signature you generate on your server matches the razorpay_signature returned to you by the Checkout form, the payment received is from an authentic source.

Generate Signature on Your Server

Given below is the sample code for payment signature verification:

RazorpayClient razorpay = new RazorpayClient("[YOUR_KEY_ID]", "[YOUR_KEY_SECRET]");

String secret = "EnLs21M47BllR3X8PSFtjtbd";

JSONObject options = new JSONObject();
options.put("razorpay_order_id", "order_IEIaMR65cu6nz3");
options.put("razorpay_payment_id", "pay_IH4NVgf4Dreq1l");
options.put("razorpay_signature", "0d4e745a1838664ad6c9c9902212a32d627d68e917290b0ad5f08ff4561bc50f");

boolean status =  Utils.verifyPaymentSignature(options, secret);

$api = new Api($key_id, $secret);

$api->utility->verifyPaymentSignature(array('razorpay_order_id' => $razorpayOrderId, 'razorpay_payment_id' => $razorpayPaymentId, 'razorpay_signature' => $razorpaySignature));

require "razorpay"
Razorpay.setup('YOUR_KEY_ID', 'YOUR_SECRET')

payment_response = {
      razorpay_order_id: 'order_IEIaMR65cu6nz3',
      razorpay_payment_id: 'pay_IH4NVgf4Dreq1l',
      razorpay_signature: '0d4e745a1838664ad6c9c9902212a32d627d68e917290b0ad5f08ff4561bc50f'
    }
Razorpay::Utility.verify_payment_signature(payment_response)

import razorpay
client = razorpay.Client(auth=("YOUR_ID", "YOUR_SECRET"))

client.utility.verify_payment_signature({
  'razorpay_order_id': razorpay_order_id,
  'razorpay_payment_id': razorpay_payment_id,
  'razorpay_signature': razorpay_signature
  })

RazorpayClient client = new RazorpayClient("[YOUR_KEY_ID]", "[YOUR_KEY_SECRET]");

Dictionary options = new Dictionary();
options.Add("razorpay_order_id", "order_IEIaMR65");
options.Add("razorpay_payment_id", "pay_IH4NVgf4Dreq1l");
options.Add("razorpay_signature", "0d4e745a1838664ad6c9c9902212a32d627d68e917290b0ad5f08ff4561bc50");

Utils.verifyPaymentSignature(options);

var instance = new Razorpay({ key_id: 'YOUR_KEY_ID', key_secret: 'YOUR_SECRET' })

var { validatePaymentVerification, validateWebhookSignature } = require('./dist/utils/razorpay-utils');
validatePaymentVerification({"order_id": razorpayOrderId, "payment_id": razorpayPaymentId }, signature, secret);

import ( razorpay "github.com/razorpay/razorpay-go" )
client := razorpay.NewClient("YOUR_KEY_ID", "YOUR_SECRET")

params := map[string]interface{}{
"razorpay_order_id": "order_IEIaMR65cu6nz3",
"razorpay_payment_id": "pay_IH4NVgf4Dreq1l",
}

signature := "0d4e745a1838664ad6c9c9902212a32d627d68e917290b0ad5f08ff4561bc50f";
secret := "EnLs21M47BllR3X8PSFtjtbd";
utils.VerifyPaymentSignature(params, signature, secret)

Post Signature Verification

After you have completed the integration, you can set up webhooks, make test payments, replace the test key with the live key and integrate with other APIs.Here are the links to our SDKs for the supported platforms.

1.6 Verify Payment Status

Handy TipsOn the Razorpay Dashboard, ensure that the payment status is captured. Refer to the payment capture settings page to know how to capture payments automatically.

You can track the payment status in three ways:

From Dashboard
Using Webhooks
Poll APIs

To verify the payment status from the Razorpay Dashboard:

Log in to the Razorpay Dashboard and navigate to Transactions → Payments.
Check if a Payment Id has been generated and note the status. In case of a successful payment, the status is marked as Captured.

You can use Razorpay webhooks to configure and receive notifications when a specific event occurs. When one of these events is triggered, we send an HTTP POST payload in JSON to the webhook’s configured URL. Know how to set up webhooks.ExampleIf you have subscribed to the order.paid webhook event, you will receive a notification every time a customer pays you for an order.

2. Test Integration

After the integration is complete, a Pay button appears on your webpage/app.

Click the button and make a test transaction to ensure the integration is working as expected. You can start accepting actual payments from your customers once the test transaction is successful.

Watch Out!This is a mock payment page that uses your test API keys, test card and payment details.

Ensure you have entered only your Test Mode API keys in the Checkout code.
Test mode features a mock bank page with Success and Failure buttons to replicate the live payment experience.
No real money is deducted due to the usage of test API keys. This is a simulated transaction.

Following are all the payment modes that the customer can use to complete the payment on the Checkout. Some of them are available by default, while others may require approval from us. Raise a request from the Dashboard to enable such payment methods.

Payment Method	Code	Availability
Debit Card	`debit`	✓
Credit Card	`credit`	✓
Netbanking	`netbanking`	✓
UPI	`upi`	✓
EMI - Credit Card EMI, Debit Card EMI and No Cost EMI	`emi`	✓
Wallet	`wallet`	✓
Cardless EMI	`cardless_emi`	Requires Approval.
Bank Transfer	`bank_transfer`	Requires Approval and Integration.
Emandate	`emandate`	Requires Approval and Integration.
Pay Later	`paylater`	Requires Approval.

You can make test payments using one of the payment methods configured at the Checkout.

Netbanking

You can select any of the listed banks. After choosing a bank, Razorpay will redirect to a mock page where you can make the payment success or a failure. Since this is Test Mode, we will not redirect you to the bank login portals.Check the list of supported banks.

UPI

You can enter one of the following UPI IDs:

success@razorpay: To make the payment successful.
failure@razorpay: To fail the payment.

Check the list of supported UPI flows.

Handy TipsYou can use Test Mode to test UPI payments, and Live Mode for UPI Intent and QR payments.

Cards

You can use the following test cards to test transactions for your integration in Test Mode.

Domestic Cards

Use the following test cards for Indian payments:

Network	Card Number	CVV & Expiry Date
Visa	4100 2800 0000 1007	Use a random CVV and any future date
Mastercard	5500 6700 0000 1002	Use a random CVV and any future date
RuPay	6527 6589 0000 1005	Use a random CVV and any future date
Diners	3608 280009 1007	Use a random CVV and any future date
Amex	3402 560004 01007	Use a random CVV and any future date

Error Scenarios

Use these test cards to simulate payment errors. See the complete list of error test cards with detailed scenarios.Check the following lists:

International Cards

Use the following test cards to test international payments. Use any valid expiration date in the future in the MM/YY format and any random CVV to create a successful payment.

Card Network	Card Number	CVV & Expiry Date
Mastercard	5555 5555 5555 4444	Use a random CVV and any future date
Mastercard	5105 1051 0510 5100	Use a random CVV and any future date
Mastercard	5104 0600 0000 0008	Use a random CVV and any future date
Visa	4012 8888 8888 1881	Use a random CVV and any future date

Check the list of supported card networks.

Wallet

You can select any of the listed wallets. After choosing a wallet, Razorpay will redirect to a mock page where you can make the payment success or a failure. Since this is Test Mode, we will not redirect you to the wallet login portals.Check the list of supported wallets.

3. Go-live Checklist

Check the go-live checklist for Razorpay Web Standard Checkout integration. Consider these steps before taking the integration live.

3.1 Accept Live Payments

Perform an end-to-end simulation of funds flow in the Test Mode. Once confident that the integration is working as expected, switch to the Live Mode and start accepting payments from customers.

Watch Out!Ensure you are switching your test API keys with API keys generated in Live Mode.

To generate API Keys in Live Mode on your Razorpay Dashboard:

Log in to the Razorpay Dashboard and switch to Live Mode on the menu.
Navigate to Account & Settings → API Keys → Generate Key to generate the API Key for Live Mode.
Download the keys and save them securely.
Replace the Test API Key with the Live Key in the Checkout code and start accepting actual payments.

3.2 Payment Capture

After payment is authorized, you need to capture it to settle the amount to your bank account as per the settlement schedule. Payments that are not captured are auto-refunded after a fixed time.

Watch Out

You should deliver the products or services to your customers only after the payment is captured. Razorpay automatically refunds all the uncaptured payments.
You can track the payment status using our Fetch a Payment API or webhooks.

Automatic Capture
Manual Capture

Authorized payments can be automatically captured. You can auto-capture all payments using global settings on the Razorpay Dashboard. Know more about capture settings for payments.

Watch Out!Payment capture settings work only if you have integrated with Orders API on your server side. Know more about the Orders API.

3.3 Set Up Webhooks

Ensure you have set up webhooks in the live mode and configured the events for which you want to receive notifications.

Implementation ConsiderationsWebhooks are the primary and most efficient method for event notifications. They are delivered asynchronously in near real-time. For critical user-facing flows that need instant confirmation (like showing “Payment Successful” immediately), supplement webhooks with API verification.Recommended approach

Rely on webhooks for all automation, which can be asynchronous.
If a critical user-facing flow requires instant status, but the webhook notification has not arrived within the time mandated by your business needs, perform an immediate API Fetch call (Payments, Orders and Refunds) to verify the status.

1. Build Integration

2. Test Integration

3. Go-live Checklist

​1. Build Integration

​Request Parameters

​Response Parameters

​Error Response Parameters

​Checkout with Handler Function

​Checkout with Callback URL

​Generate Signature on Your Server

​Post Signature Verification

​2. Test Integration

​Domestic Cards

​Error Scenarios

​International Cards

​3. Go-live Checklist

1. Build Integration

Request Parameters

Response Parameters

Error Response Parameters

Checkout with Handler Function

Checkout with Callback URL

Generate Signature on Your Server

Post Signature Verification

2. Test Integration

Domestic Cards

Error Scenarios

International Cards

3. Go-live Checklist