1. Build Integration

Steps to integrate Razorpay Payment Gateway with .NET SDK.


Follow the steps given below to integrate Razorpay Payment Gateway with your .Net website. The integration process is explained using the .NET sample app, which contains the following files:

File Name

Purpose

Payment.aspx

Contains the code to invoke Razorpay Checkout.

Payment.aspx.cs

Contains the code for order creation using Orders API.

Charge.cs

Contains the code for verifying payment signature.

To integrate the Payment Gateway on your .NET website:

1.1 Create an order in Server.

1.2 Add the checkout code.

1.3 Store fields in server.

1.4 Verify payment signature.

1.5 Verify payment status.

1.1 Create an Order in Server🔗

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.

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.

Handy Tips
You can capture payments automatically with the one-time Payment Capture setting configuration on the Razorpay Dashboard.

API Sample Code🔗

In the sample app, the Payment.aspx.cs file contains the code for order creation using Orders API.

CopyDictionary<string, object> input = new Dictionary<string, object>(); input.Add("amount", 100); // this amount should be same as transaction amount input.Add("currency", "INR"); input.Add("receipt", "12121"); string key = "<Enter your Api Key here>"; string secret = "<Enter your Api Secret here>"; RazorpayClient client = new RazorpayClient(key, secret); Razorpay.Api.Order order = client.Order.Create(input); orderId = order["id"].ToString();

Request Parameters🔗

Here is the list of parameters for creating an order:

amount mandatory
integer The transaction amount, expressed in the currency subunit, such as paise (in case of INR). For example, for an actual amount of ₹299.35, the value of this field should be 29935.
currency mandatory
string The currency in which the transaction should be made. See the list of supported currencies. Length must be of 3 characters.
receipt optional
string Pass receipt id for this order. Maximum length 40 characters.
notes optional
json object Key-value pair 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 the customer must pay as the first partial payment. For example, if an amount of ₹7,000 is to be received from the customer in two instalments 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.

Know more about Orders API.

Error Response Parameters🔗

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

1.2 Add Checkout Code🔗

In the sample app, the Payment.aspx file contains the code to invoke Razorpay Checkout. This is the code that creates a Pay button on your website. When your customers click on this button, the Razorpay Checkout form appears.

Handy Tips
Ensure you do the following while using the sample app:

  • Edit the [KEY_ID] inside Payment.aspx. Use the test keys while testing your application. Know how to Generate API keys.
  • Edit the [key_id] and [key_secret] in charge.aspx.
  • Enforce the appropriate TLS version in the app, as shown:
CopySystem.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;

Code to Add Pay Button🔗

Copy-paste the parameters as options in your code:

Copy<!DOCTYPE html> <html xmlns="http://www.w3.org/1999/xhtml"> <head runat="server"> <title>Razorpay .Net Sample App</title> <form action="Charge.aspx" method="post" name="razorpayForm"> <input id="razorpay_payment_id" type="hidden" name="razorpay_payment_id" /> <input id="razorpay_order_id" type="hidden" name="razorpay_order_id" /> <input id="razorpay_signature" type="hidden" name="razorpay_signature" /> </form> </head> <body> <button id="rzp-button1">Pay with Razorpay</button> <script src="https://checkout.razorpay.com/v1/checkout.js"></script> <script> var orderId = "<%=orderId%>" var options = { "name": "Acme Corp", "description": "Buy Green Tea", "order_id": orderId, "image": "https://example.com/your_logo", "prefill": { "name": "Gaurav Kumar", "email": "gaurav.kumar@example.com", "contact": "+919999999999", }, "notes": { "address": "Hello World" }, "theme": { "color": "#3399cc" } } // Boolean whether to show image inside a white frame. (default: true) options.theme.image_padding = false; options.handler = function (response) { document.getElementById('razorpay_payment_id').value = response.razorpay_payment_id; document.getElementById('razorpay_order_id').value = orderId; document.getElementById('razorpay_signature').value = response.razorpay_signature; document.razorpayForm.submit(); }; options.modal = { ondismiss: function () { console.log("This code runs when the popup is closed"); }, // Boolean indicating whether pressing escape key // should close the checkout form. (default: true) escape: true, // Boolean indicating whether clicking translucent blank // space outside checkout form should close the form. (default: false) backdropclose: false }; var rzp = new Razorpay(options); document.getElementById('rzp-button1').onclick = function (e) { rzp.open(); e.preventDefault(); } </script> </body> </html>

Checkout Options🔗

key mandatory

string API Key ID generated from the Razorpay Dashboard.

amount mandatory

integer The amount to be paid by the customer in currency subunits. For example, if the amount is ₹100, enter 10000.

currency mandatory

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

name mandatory

string The business name shown on the Checkout form.

description optional

string Description of the purchase item shown on the Checkout form. Must 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 loading the image from a network is not desirable.

order_id mandatory

string Order ID generated via Razorpay Orders API.

prefill

object You can prefill the following details at Checkout.

name optional
string Cardholder's name to be pre-filled if customer is to make card payments on Checkout.
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, 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
string Pre-selection of the payment method for the customer. Will only work if contact and email are also pre-filled. Possible values
  • card
  • netbanking
  • wallet
  • emi
  • upi
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.

hide_topbar optional
boolean Used to display or hide the top bar on the Checkout form. This bar shows the selected payment method, phone number and gives the customer the option to navigate back to the start of the Checkout form. Possible values are:
  • true: Hides the top bar
  • false (default): Displays the top bar.
color optional
string Enter your brand colour's HEX code to alter the appearance of 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 are:
  • 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 are:
  • 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 when customers attempt 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.
animation optional
boolean Show an animation before loading of Checkout.
  • 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.

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. 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.
recurring optional

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: You are accepting recurring payments.
  • false (default): You are not accepting recurring payments.
callback_url optional

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

redirect optional

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.
customer_id optional

string Unique identifier of customer. Used for:

timeout optional

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

remember_customer optional

boolean Determines whether to allow saving of cards. Can also be configured via the Razorpay Dashboard. Possible values:

  • true: Enables card saving feature.
  • false (default): Disables card saving feature.
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.
send_sms_hash optional

boolean Used to auto-read OTP for cards and net banking 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.
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.
retry optional

object Parameters that enable retry of payment on the checkout.

enabled
boolean 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
integer The number of times the customer can retry the payment. Recommended to set this to 4. Having a larger number here can cause loops to occur.
config optional

object Parameters that enable configuration of checkout display language.

display

object Child parameter that enables configuration of checkout display language.

language
string The language in which checkout should be displayed. Possible values:
  • en: English
  • ben: Bengali
  • hi: Hindi
  • mar: Marathi
  • guj: Gujarati
  • tam: Tamil
  • tel: Telugu

Configure Payment Methods🔗

Multiple payment methods are available on Razorpay 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 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.

Copy{ "razorpay_payment_id": "pay_29QQoUBi66xm2f", "razorpay_order_id": "order_9A33XWu170gUtm", "razorpay_signature": "9ef4dffbfd84f1318f6739a3ce19f9d85851857ae648f114332d8401e0949a3d" }
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.

1.4 Verify Payment Signature🔗

This is a mandatory step to confirm the authenticity of the details returned to the Checkout form for successful payments. In the sample app, the Charge.cs file contains the code for verifying payment signature.

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 Razorpay Dashboard.
  2. Use the SHA256 algorithm, the razorpay_payment_id and the order_id to construct an HMAC hex digest as shown below:

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

Generate Signature on Your Server🔗

Copy Dictionary<string, string> attributes = new Dictionary<string, string>(); attributes.Add("razorpay_payment_id", paymentId); attributes.Add("razorpay_order_id", Request.Form["razorpay_order_id"]); attributes.Add("razorpay_signature", Request.Form["razorpay_signature"]); Utils.verifyPaymentSignature(attributes);

1.5 Verify Payment Status🔗

You can track the payment status from the Razorpay Dashboard, subscribe to the Webhook event or poll our APIs.

Verify Payment Status From Dashboard🔗

  1. Log into the 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.

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.

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.

Poll APIs🔗

Poll Payment APIs to check the payment status.

×