> ## Documentation Index
> Fetch the complete documentation index at: https://doc-test-my.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Integration Steps

> Steps to integrate the Standard Checkout form on your website.

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

<CardGroup cols={3}>
  <Card title="1. Build Integration" href="/docs/payments/payment-gateway/web-integration/standard/integration-steps#1-build-integration">
    Integrate Web Standard Checkout.
  </Card>

  <Card title="2. Test Integration" href="/docs/payments/payment-gateway/web-integration/standard/integration-steps#2-test-integration">
    Test the integration by making a test payment.
  </Card>

  <Card title="3. Go-live Checklist" href="/docs/payments/payment-gateway/web-integration/standard/integration-steps#3-go-live-checklist">
    Check the go-live checklist.
  </Card>
</CardGroup>

## 1. Build Integration

Follow the steps given below:

<AccordionGroup>
  <Accordion title="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. <ul><li>No more payment requests are allowed after an order moves to the **paid** state. </li><li> The order continues to be in this state even if the payment for this order is **refunded**.</li></ul> |

    <Info>
      **Capture Payments Automatically**

      You can capture payments automatically with the one-time [Payment Capture setting configuration](/docs/payments/payments/capture-settings) on the Dashboard.
    </Info>

    **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](#api-sample-code). It is a server-side API call. Know how to [authenticate](/docs/payments/dashboard/account-settings/api-keys#generate-api-keys) 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.

    <Warning>
      **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.
    </Warning>

    ### API Sample Code

    Use this endpoint to create an order using the Orders API.

    `POST /orders`

    <CodeGroup>
      ```bash Curl theme={null}
      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": "MYR",
          "receipt": "qwsaq1",
          "partial_payment": true,
          "first_payment_min_amount": 230
      }'
      ```

      ```java Java theme={null}
      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", "MYR");
        orderRequest.put("receipt", "order_rcptid_11");
        Order order = razorpay.Orders.create(orderRequest);
      } catch (RazorpayException e) {
        // Handle Exception
        System.out.println(e.getMessage());
      }
      ```

      ```python Python theme={null}
      import razorpay
      client = razorpay.Client(auth=("YOUR_ID", "YOUR_SECRET"))
      DATA = {
          "amount": 50000,
          "currency": "MYR",
          "receipt": "receipt#1",
          "notes": {
              "key1": "value3",
              "key2": "value2"
          }
      }
      client.order.create(data=DATA)
      ```

      ```php PHP theme={null}
      $api = new Api($key_id, $secret);
      $api->order->create(array('receipt' => '123', 'amount' => 50000, 'currency' => 'MYR', 'notes'=> array('key1'=> 'value3','key2'=> 'value2')));
      ```

      ```csharp .NET theme={null}
      RazorpayClient client = new RazorpayClient(your_key_id, your_secret);
      Dictionary<string, object> options = new Dictionary<string,object>();
      options.Add("amount", 50000); // amount in the smallest currency unit
      options.add("receipt", "order_rcptid_11");
      options.add("currency", "MYR");
      Order order = client.Order.Create(options);
      ```

      ```ruby Ruby theme={null}
      require "razorpay"
      Razorpay.setup('YOUR_KEY_ID', 'YOUR_SECRET')
      options = amount: 50000, currency: 'MYR', receipt: '<order_rcptid_11>'
      order = Razorpay::Order.create
      ```

      ```javascript Node.js theme={null}
      var instance = new Razorpay({ key_id: 'YOUR_KEY_ID', key_secret: 'YOUR_SECRET' })
      instance.orders.create({
        amount: 50000,
        currency: "MYR",
        receipt: "receipt#1",
        notes: {
          key1: "value3",
          key2: "value2"
        }
      })
      ```

      ```go Go theme={null}
      import ( razorpay "github.com/razorpay/razorpay-go" )
      client := razorpay.NewClient("YOUR_KEY_ID", "YOUR_SECRET")
      data := map[string]interface{}{
        "amount": 50000,
        "currency": "MYR",
        "receipt": "some_receipt_id"
      }
      body, err := client.Order.Create(data)
      ```

      ```json Success Response theme={null}
      {
          "id": "order_IluGWxBm9U8zJ8",
          "entity": "order",
          "amount": 50000,
          "amount_paid": 0,
          "amount_due": 50000,
          "currency": "MYR",
          "receipt": "rcptid_11",
          "offer_id": null,
          "status": "created",
          "attempts": 0,
          "notes": [],
          "created_at": 1642662092
      }
      ```

      ```json Failure Response theme={null}
      {
      "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"
      }
      }
      ```
    </CodeGroup>

    <AccordionGroup>
      <Accordion title="Request Parameters">
        `amount` *mandatory*
        : `integer` The transaction amount, expressed in the currency subunit. For example, for an actual amount of , the value of this field should be `22225`.

        `currency` *mandatory*
        : `string` The currency in which the transaction should be made.  See the [list of supported currencies](/docs/payments/international-payments#supported-currencies). Length must be of 3 characters.

        `receipt` *optional*
        : `string` Your receipt id for this order should be passed here. Maximum length is 40 characters.

        `notes` *optional*
        : `json 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”`.

        `partial_payment` *optional*
        : `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.

        `first_payment_min_amount` *optional*
        : `integer` Minimum amount that must be paid by the customer as the first partial payment. For example, if an amount of  is to be received from the customer in two installments of #1 - RM 5,000, #2 - RM 2,000, then you can set this value as `500000`. This parameter should be passed only if `partial_payment` is `true`.
      </Accordion>

      <Accordion title="Response Parameters">
        Descriptions for the response parameters are present in the [Orders Entity](/docs/api/orders/entity) parameters table.
      </Accordion>

      <Accordion title="Error Response Parameters">
        The error response parameters are available in the [API Reference Guide](/docs/api/orders/create).
      </Accordion>
    </AccordionGroup>
  </Accordion>

  <Accordion title="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.

    <Info>
      **Handy Tips** <br />

      For FPX payments, you must use the Callback URL sample code for checkout. You should send the following parameters along with the other checkout parameters:

      * `callback_url` with the URL to which customers should be redirected after payment completion.
      * `redirect` with the value as `true`.
    </Info>

    <AccordionGroup>
      <Accordion title="2.1 Handler Function or Callback URL">
        | **Handler Function**                                                                                                                                                                           | **Callback URL**                                                                                                                                                                                                    |
        | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | When you use this: <ul><li>On successful payment, the customer is shown your web page. </li><li> On failure, the customer is notified of the failure and asked to retry the payment.</li></ul> | When you use this: <ul><li>On successful payment, the customer is redirected to the specified URL, for example, a payment success page. </li><li> On failure, the customer is asked to retry the payment.</li></ul> |
      </Accordion>
    </AccordionGroup>

    <Info>
      **Heads up: callback\_url and your webhook URL are different**

      The callback\_url Checkout option is only for WebView and redirect flows. For standard web integrations, use the handler function to handle payment completion on the client side, and webhooks for server-side confirmation. See [Webhooks](/docs/webhooks) for details.

      If you use callback\_url in a standard web integration, it bypasses the handler function and the payment status will not be confirmed on the client side immediately after payment.
    </Info>

    <AccordionGroup>
      <Accordion title="2.2 Code to Add Pay Button">
        Copy-paste the parameters as `options` in your code:

        <CodeGroup>
          ```html Callback URL (JS) Checkout Code theme={null}
          <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": "MYR",
              "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": "<name>", //your customer's name
                  "email": "<email>",
                  "contact": "<phone>" //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>
          ```

          ```html Handler Functions (JS) Checkout Code theme={null}
          <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": "MYR",
              "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": "<name>", //your customer's name
                  "email": "<email>", 
                  "contact": "<phone>"  //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>
          ```
        </CodeGroup>

        <Info>
          **Handy Tips**

          Test your integration using these [test cards](/docs/payments/payment-gateway/web-integration/standard/integration-steps#2-test-integration).
        </Info>
      </Accordion>

      <Accordion title="2.3 Checkout Options">
        `key` *mandatory*
        : `string` API Key ID generated from the Dashboard.

        `amount` *mandatory*
        : `integer` The amount to be paid by the customer in sen. For example, if the amount is , enter `222250`.

        `currency` *mandatory*
        : `string` The currency in which the payment should be made by the customer. Length must be of 3 characters.

        `name` *mandatory*
        : `string` Your Business/Enterprise name shown on the Checkout form. For example, **Acme Corp**.

        `description` *optional*
        : `string` Description of the purchase item shown on the Checkout form. It should start with an alphanumeric character.

        `image` *optional*
        : `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.

        `order_id` *mandatory*
        : `string` Order ID generated via [Orders API](/docs/api/orders).

        `prefill`
        : `object` You can prefill the following details at Checkout.

        <Info>
          **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": "+603112345678".
          * 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.
        </Info>

        `name` *optional*
        : `string` Cardholder's name to be prefilled if customer is to make card payments on Checkout. For example, **Siti Aisyah**.

        `email` *optional*
        : `string` Email address of the customer.

        `contact` *optional*
        : `string` Phone number of the customer. The expected format of the phone number is `+ {country code}{phone number}`. If the country code is not specified, `60` will be used as the default value. This is particularly important while prefilling `contact` of customers with phone numbers issued outside Malaysia. **Examples**:

        * +14155552671 (a valid non-Malaysian number)
        * +603112345678 (a valid Malaysian number). <br />If 1113455567 is entered without the country code, `+60` is added to it as +601113455567.

        `method` *optional*
        : `string` Pre-selection of the payment method for the customer. Will only work if `contact` and `email` are also prefilled. <br /> Possible value is `card`.

        `notes` *optional*
        : `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).

        `theme`
        : `object` Thematic options to modify the appearance of Checkout.

        `color` *optional*
        : `string` 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*
        : `string` Enter a HEX code to change the Checkout's backdrop colour.

        `modal`
        : `object` Options to handle the Checkout modal.

        `backdropclose` *optional*
        : `boolean` 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 the checkout form.
        * `false` (default): Does not close the form when customer clicks outside the checkout form.

        `escape` *optional*
        : `boolean` Indicates whether pressing the **escape** key should close the Checkout form. Possible values:

        * `true` (default): Closes the form when the customer presses the **escape** key.
        * `false`: Does not close the form when the customer presses the **escape** key.

        `handleback` *optional*
        : `boolean` Determines whether Checkout must behave similar to the browser when back button is pressed. Possible values:

        * `true` (default): Checkout behaves similarly to the browser. That is, when the browser's back button is pressed, the Checkout also simulates a back press. This happens as long as the Checkout modal is open.
        * `false`: Checkout does not simulate a back press when browser's back button is pressed.

        `confirm_close` *optional*
        : `boolean` 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): Confirmation dialog box is not shown.

        `ondismiss` *optional*
        : `function` 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. If `retry` is `false`, the `ondismiss` function is triggered when checkout closes, even after a failure.

        `animation` *optional*
        : `boolean` Shows an animation before loading of Checkout. Possible values:

        * `true`(default): Animation appears.
        * `false`: Animation does not appear.

        `subscription_id` *optional*
        : `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](/docs/api/payments/subscriptions-custom#checkout-integration).

        `subscription_card_change` *optional*
        : `boolean` Permit or restrict customer from changing the card linked to the subscription. You can also do this from the [hosted page](/docs/payments/subscriptions/payment-retries#update-the-payment-method-via-our-hosted-page). Possible values:

        * `true`: Allow the customer to change the card from Checkout.
        * `false` (default): Do not allow the customer to change the card from Checkout.

        `callback_url` *optional*
        : `string` Customers will be redirected to this URL on successful payment. Ensure that the domain of the Callback URL is allowlisted. This parameter is mandatory for FPX payments.

        `redirect` *optional*
        : `boolean` Determines whether to post a response to the event handler post payment completion or redirect to Callback URL. `callback_url` and `redirect` parameters are mandatory for FPX payments. Possible values:

        * `true`: Customer is redirected to the specified callback URL in case of payment failure. For FPX payments, the `redirect` parameter should always be sent as `true`.
        * `false` (default): Customer is shown the Checkout popup to retry the payment.

        `customer_id` *optional*
        : `string` Unique identifier of customer.

        `remember_customer` *optional*
        : `boolean` Determines whether to allow saving of cards. Can also be configured via the [Dashboard](/docs/payments/dashboard/account-settings/checkout-features#flash-checkout). Possible values:

        * `true`: Enables card saving feature.
        * `false` (default): Disables card saving feature.

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

        <Warning>
          **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.
        </Warning>

        `readonly`
        : `object` Marks fields as read-only.

        `contact` *optional*
        : `boolean` Used to set the `contact` field as readonly. Possible values:

        * `true`: Customer will not be able to edit this field.
        * `false` (default): Customer will be able to edit this field.

        `email` *optional*
        : `boolean` Used to set the `email` field as readonly. Possible values:

        * `true`: Customer will not be able to edit this field.
        * `false` (default): Customer will be able to edit this field.

        `name` *optional*
        : `boolean` Used to set the `name` field as readonly. Possible values:

        * `true`: Customer will not be able to edit this field.
        * `false` (default): Customer will be able to edit this field.

        `hidden`
        : `object` Hides the contact details.

        `contact` *optional*
        : `boolean` Used to set the `contact` field as optional. Possible values:

        * `true`: Customer will not be able to view this field.
        * `false` (default): Customer will be able to view this field.

        `email` *optional*
        : `boolean` Used to set the `email` field as optional. Possible values:

        * `true`: Customer will not be able to view this field.
        * `false` (default): Customer will be able to view this field.

        `send_sms_hash` *optional*
        : `boolean` Used to auto-read OTP for cards. Applicable from Android SDK version 1.5.9 and above. Possible values:

        * `true`: OTP is auto-read.
        * `false` (default): OTP is not auto-read.

        `allow_rotation` *optional*
        : `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.

        `config` *optional*
        : `object` Parameters that enable checkout configuration. Know more about how to [configure payment methods on Razorpay standard checkout](/docs/payments/payment-gateway/web-integration/standard/configure-payment-methods).

        `display`
        : `object` Child parameter that enables configuration of checkout display language.

        `language`
        : `string` The language in which checkout should be displayed. Possible value is `en`: English.

        <Info>
          **Handy Tips**

          The 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.
        </Info>
      </Accordion>

      <Accordion title="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`. |
        | 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.                                               |
      </Accordion>

      <Accordion title="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](/docs/payments/payment-gateway/web-integration/standard/configure-payment-methods).
      </Accordion>
    </AccordionGroup>
  </Accordion>

  <Accordion title="3 Handle Payment Success and Failure">
    The way the Payment Success and Failure scenarios are handled depends on the [Checkout Sample Code](#122-code-to-add-pay-button) you used in the last step.

    ### Checkout with Handler Function

    If you used the sample code with the handler function:

    <Tabs>
      <Tab title="Payment Success">
        #### On Payment Success

        The 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.
      </Tab>

      <Tab title="Payment Failure">
        #### On Payment Failure

        The customer is notified about payment failure and asked to retry the payment. Know about the [error parameters.](/docs/errors#response-parameters)

        ```javascript Failure Handling Code theme={null}
        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);
        }
        ```
      </Tab>
    </Tabs>

    ### Checkout with Callback URL

    If you used the sample code with the callback URL:

    <Tabs>
      <Tab title="Payment Success">
        #### On Payment Success

        Razorpay 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.
      </Tab>

      <Tab title="Payment Failure">
        #### On Payment Failure

        In case of failed payments, the checkout is displayed again to facilitate payment retry.
      </Tab>
    </Tabs>
  </Accordion>

  <Accordion title="4 Store Fields in Your Server">
    A successful payment returns the following fields to the Checkout form.

    <AccordionGroup>
      <Accordion title="Success Callback">
        * 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.

        <CodeGroup>
          ```json Success Callback theme={null}
          {
            "razorpay_payment_id": "pay_29QQoUBi66xm2f",
            "razorpay_order_id": "order_9A33XWu170gUtm",
            "razorpay_signature": "9ef4dffbfd84f1318f6739a3ce19f9d85851857ae648f114332d8401e0949a3d"
          }
          ```
        </CodeGroup>

        <br />

        `razorpay_payment_id`
        : `string` Unique identifier for the payment returned by Checkout **only** for successful payments.

        `razorpay_order_id`
        : `string` Unique identifier for the order returned by Checkout.

        `razorpay_signature`
        : `string` Signature returned by the Checkout. This is used to verify the payment.
      </Accordion>
    </AccordionGroup>
  </Accordion>

  <Accordion title="5 Verify Payment Signature">
    This is a mandatory step to confirm the authenticity of the details returned to the Checkout form for successful payments.

    <AccordionGroup>
      <Accordion title="To verify the `razorpay_signature` returned to you by the Checkout form:">
        1. 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](/docs/payments/dashboard/account-settings/api-keys#generate-api-keys).

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

        ```html HMAC Hex Digest theme={null}
        generated_signature = hmac_sha256(order_id + "|" + razorpay_payment_id, secret);

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

        3. 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.
      </Accordion>
    </AccordionGroup>

    <AccordionGroup>
      <Accordion title="Generate Signature on Your Server">
        Given below is the sample code for payment signature verification:

        <CodeGroup>
          ```java Java theme={null}
          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);
          ```

          ```php PHP theme={null}
          $api = new Api($key_id, $secret);

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

          ```ruby Ruby theme={null}
          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)
          ```

          ```python Python theme={null}
          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
            })
          ```

          ```c .NET theme={null}
          RazorpayClient client = new RazorpayClient("[YOUR_KEY_ID]", "[YOUR_KEY_SECRET]");

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

          Utils.verifyPaymentSignature(options);
          ```

          ```javascript Node.js theme={null}
          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);
          ```

          ```go Go theme={null}
          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)
          ```
        </CodeGroup>
      </Accordion>
    </AccordionGroup>

    <AccordionGroup>
      <Accordion title="Post Signature Verification">
        After you have completed the integration, you can [set up webhooks](/docs/webhooks/setup-edit-payments), make test payments, replace the test key with the live key and integrate with other [APIs](/docs/api).
      </Accordion>
    </AccordionGroup>

    <Warning>
      **Watch Out: Always verify the payment signature server-side**

      After a payment completes, Razorpay sends `razorpay_payment_id`, `razorpay_order_id` and `razorpay_signature` to your handler. You must verify the signature on your server before fulfilling the order.

      A failed signature check indicates a potentially fraudulent or tampered payment. Reject the order entirely — do not fulfil it, do not retry and do not treat it as a genuine payment. Skipping this step is the most common cause of fraudulent orders and payment disputes.
    </Warning>

    Here are the links to our [SDKs](/docs/payments/payment-gateway/web-integration/standard#client-libraries) for the supported platforms.
  </Accordion>

  <Accordion title="6 Verify Payment Status">
    <Info>
      **Handy Tips**

      On the Razorpay Dashboard, ensure that the payment status is `captured`. Refer to the payment capture settings page to know how to [capture payments automatically](/docs/payments/payments/capture-settings).
    </Info>

    <AccordionGroup>
      <Accordion title="You can track the payment status in three ways:">
        <Tabs>
          <Tab title="Verify Status from Dashboard">
            To verify the payment status from the Razorpay Dashboard:

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

            <img class="click-zoom" src="https://curlec.com/docs/build/browser/assets/images/my-testpayment.jpg" width="800" alt="Payment details on Dashboard" />
          </Tab>

          <Tab title="Subscribe to Webhook Events">
            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.](/docs/webhooks/setup-edit-payments)

            #### Example

            If you have subscribed to the `order.paid` webhook event, you will receive a notification every time a customer pays you for an order.
          </Tab>

          <Tab title="Poll APIs">
            [Poll Payment APIs](/docs/api/payments/fetch-all-payments) to check the payment status.
          </Tab>
        </Tabs>
      </Accordion>
    </AccordionGroup>
  </Accordion>
</AccordionGroup>

## 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.

<Warning>
  **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](/docs/payments/dashboard/account-settings/api-keys#generate-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.
</Warning>

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 and Credit Cards](/docs/payments/payment-methods/cards) | `card`   | ✓            |
| [FPX](/docs/payments/payment-methods/fpx)                      | `fpx`    | ✓            |
| [Wallets](/docs/payments/payment-methods/wallets)              | `wallet` | ✓            |

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

<AccordionGroup>
  <Accordion title="FPX">
    You can select any of the listed banks. After choosing a bank, Razorpay Curlec will redirect to a mock page where you can make the payment a `success` or a `failure`. Since this is Test Mode, we will not redirect you to the bank login portals.
  </Accordion>

  <Accordion title="Wallet">
    You can select any of the listed wallets. After choosing a wallet, you will be redirected 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.

    <Warning>
      **Watch Out!**

      iOS integration for Touch'n Go wallet is currently unavailable. We will be adding support for it soon.
    </Warning>
  </Accordion>

  <Accordion title="Cards">
    You can use one of the following test cards to test transactions for your integration in Test Mode.

    | Card Network | Card Number         | CVV & Expiry Date                       |
    | ------------ | ------------------- | --------------------------------------- |
    | Mastercard   | 5272 0088 0623 5704 | Use a random CVV and any future date ^^ |
    | Visa         | 4842 7930 0208 6571 |                                         |

    Check the following lists:

    * [Supported Card Networks](/docs/payments/payment-methods/cards).
    * [Cards Error Codes](/docs/errors/payments/cards).
  </Accordion>
</AccordionGroup>

## 3. Go-live Checklist

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

<AccordionGroup>
  <Accordion title="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.

    <Warning>
      **Watch Out!**

      Ensure you are switching your test API keys with API keys generated in Live Mode.
    </Warning>

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

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

    <br />

    <Warning>
      **Watch Out: Swap your API keys before going live**

      Your Test Mode API keys only process simulated transactions — no real money moves. If you go live without replacing them with Live Mode keys, customers will see a payment success screen but no payment will be captured or settled.

      Generate your Live Mode keys from Dashboard → **Account & Settings** → **API Keys** → **Generate Key** (switch to Live Mode first).
    </Warning>
  </Accordion>

  <Accordion title="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.

    <Warning>
      **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](/docs/api/payments#fetch-a-payment) or webhooks.
    </Warning>

    <Tabs>
      <Tab title="Auto-capture Payments (Recommended)">
        Authorized payments can be automatically captured. You can auto-capture all payments [using global settings](/docs/payments/payments/capture-settings#auto-capture-all-payments) on the Razorpay Dashboard. Know more about [capture settings for payments](/docs/payments/payments/capture-settings).

        <Warning>
          **Watch Out!**

          Payment capture settings work only if you have integrated with Orders API on your server side. Know more about the [Orders API](/docs/api/orders/create).
        </Warning>
      </Tab>

      <Tab title="Manually Capture Payments">
        Each authorized payment can also be captured individually. You can manually capture payments using [Payment Capture API](/docs/api/payments/capture) or [Dashboard](/docs/payments/payments/dashboard#manually-capture-payments). Know more about [capture settings for payments](/docs/payments/payments/capture-settings).
      </Tab>
    </Tabs>

    <Warning>
      **Watch Out: Authorised payments must be captured to settle**

      A payment in `authorized` state has been approved by the bank but not yet settled to your account. You must capture it — either manually from the Dashboard or automatically via capture settings.

      Uncaptured payments are auto-refunded after a fixed period. If customers are paying but you are not seeing settlements, check your capture settings in Dashboard → **Account & Settings** → **Payment Capture**.
    </Warning>
  </Accordion>

  <Accordion title="3 Set Up Webhooks">
    Ensure you have [set up webhooks](/docs/webhooks/setup-edit-payments) in the live mode and configured the events for which you want to receive notifications.

    <Warning>
      **Implementation Considerations**

      Webhooks 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** <br />

      * 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](/docs/api/payments/fetch-with-id), [Orders](/docs/api/orders/fetch-with-id) and [Refunds](/docs/api/refunds/fetch-specific-refund-payment)) to verify the status.
    </Warning>
  </Accordion>
</AccordionGroup>