Existing card details will be saved as network tokens irrespective of whether the The Collect Consent from Customers feature is enabled on the Razorpay Dashboard or not, provided consent_to_save_card=1.

If the customer does not consent, the card details will not be saved.

Existing cards are cards whose details have been previously saved with Razorpay on Razorpay servers.

Customers can delete their card details by visiting this link and following the on-screen instructions.

sing Saved Card🔗

you

Changes on checkout UI. Changes on Razorpay Dashboard. Changes in integration code.

In this scenario, you should follow the steps given below:

New cards are cards that have previously not been saved with Razorpay.

Scenario 1 - Business Seeks Customer Consent and Allows Card Saving

Business will seek customer consent on their UI and will save card details with Razorpay.

Business can Seek Consent from some Customers Only.

Card Tokenisation Scenarios🔗

Related Info🔗

According to RBI Guidelines, only card networks can tokenise cards. Also, tokenisation is permitted only after the customer provides explicit consent. In light of these guidelines, the process for card tokenisation will differ on a case-to-case basis.

Save Customer Card Details as Network Tokens

as follows:

using Tokens🔗

Generate API Keys from the Dashboard.

In an online transaction using UPI collect flow, customers enter their virtual payment address (VPA) on the custom Checkout, open their respective UPI apps and complete the payment after successful two-factor authentication. Customers are redirected to your website after successful payment. In this flow, it is likely that the customers enter invalid VPAs or forget their VPAs, which could lead to higher drop-off rates. To overcome this problem, Razorpay enables you to save the VPAs of a customer. The VPAs entered by the customer is stored and secured as tokens in Razorpay. This saves the customer the hassle of entering the VPA again for every transaction. After that, the customers select the saved VPA and complete the payment on subsequent visits.

on

VPAs are saved as tokens

utilize

There might be cases when you have to display the available EMI plans on the Checkout and your site. In such cases, you can use the Razorpay checkout helper methods to fetch the details of the EMI plans and display them on your site. You can use the event ready, as shown below:

EMI Plans

Format of data object and success/error handlers remain the same as before.

Now you can make AJAX requests. Once done, you can emit resume or cancel the event:

Since the createPayment method must be called synchronously within user-initiated action, the method above doesn't work if the popup blocker is enabled. You can decouple popup opening and payment creation if you need to perform any asynchronous operation, such as sending an AJAX request before starting payment.

This helps as a visual reminder to the customer that the payment is ongoing.

to the forefront

Bring a Popup to the Front

Watch Out! You should provide the user's contact number with the country code to check the eligibility.

You can see it in action here:

Pass the method and provider parameters during Payment Creation🔗

Sample checkout code to collect the authorization transaction🔗

Recurring Payments API documentation.

know more about the Saved Cards feature.

in this case are:

Know more about integrating bank transfer with Custom Checkout.

You can now pass the vpa parameter in the upi array as shown below:

Know more about Validate VPA and Saved VPA.

Know more about how to verify payment signature.

While Razorpay strives to provide a positive payment experience to every customer, they might face payment exceptions such as:

To overcome such exceptions and provide a smooth payment experience to your customers, use the Payments Rainy Day kit.

Integrate the Payments Rainy Day Kit🔗

You can configure payment methods, orders, company logo and select custom colours based on your convenience. This checkout supports all the major browsers (IE 9 and above).

Custom Checkout is an integration provided by Razorpay where you can completely customize the checkout as per your requirements and use it as a white label solution.

You can do this by invoking createPayment method:

Include the script from https://checkout.razorpay.com/v1/razorpay.js instead of serving a copy from your server. This allows the library's new updates and bug fixes to fit your application automatically. We always maintain backward compatibility with our code.

.

PCI DSS

All payments received on the unregistered websites are failed by Razorpay.

on

With Custom Checkout, you can build a checkout form to suit your unique business needs and branding guidelines.

This error message is displayed if the Webhook is not configured correctly on the Razorpay Dashboard. To fix this error, check the reasons and their solutions:

Note:

Note:

Before connecting your account with the Wix platform, you need to set up Webhook on the Razorpay Dashboard. If you do not set up Webhook, there may be connection errors.

Webhook

Wix Integration - FAQs

order.paid refund.processed payment.failed

t is mandatory to set up a webhook secret. Skipping this can lead to errors. The secret can be a combination of letters, numbers and special characters. The secret entered here is used to validate that the webhook is from Razorpay. Do not expose the secret publicly.

Watch the short animation below for more details.

Sign up for a Wix Account.

Verify the Signature🔗

list of checkout options available.

failed payments

uccessful payment

This integration method provides a default Razorpay Pay with Razorpay button that invokes the Checkout form. The Checkout form options are passed as data attributes inside a <script> tag. You can add any additional, hidden or visible fields to the form, which will be submitted along with the form.

Follow the steps complete Quick Integration:

List of other integration methods is available here.

Know more.

Cordova

Troubleshooting and FAQs Address Verification System Webhooks (Recommended) Error Codes (Recommended) How Payment Gateway Works Payment States Settlements Refunds Accept UPI payments

Ionic serve does not support cordova browser plugins, we do not support ionic serve at the moment.

This error occurs with Modulesgarden-enabled WHMCS installation. Modulesgarden plugins update system_url from example.com to example.com/, which changes the URL from "example.com/modules/gateways/callback/razorpay.php" to "example.com//modules/gateways/callback/razorpay.php". Due to this, the HTTP POST request stops working. To solve this issue, remove "/" in "/modules/gateways/callback/razorpay.php".

Web Host Manager Complete Solution (WHMCS) Integration - FAQs

. Learn more about how to validate webhooks.

Please refer to the test webhooks section for alternatives to localhost.

set-up

Learn more about Webhooks setup.

in the drop down

Unzip and upload the contents of the repository to your WHMCS Installation directory, that is the content of module folder from the repository goes in module folder in your WHMCS Installation directory.

version 2.0.1.

release tagged version 1.0.3.

Integrate Razorpay With Web Host Manager Complete Solution (WHMCS)

Generate the API keys from the Razorpay Dashboard by navigating to Settings → API Keys. You can use the Test mode keys for testing and later switch to Live mode keys when going live with the integration.

we support the following versions of WHMCS:

Currently

Click here for more details.

This issue is caused by the new changes introduced in Xcode 12.

Navigate to iOS folder in your project and run 'pod update' to update all the pods. If you do not want to update all pods, run 'pod update razorpay-pod'

If you think of a new feature that can add more value or if it should be included in our plugin, please raise a pull request or create a feature request from New Issue → Feature Request on our GitHub repository.

Learn more about Orders.

dependencies.

No

To work around this issue:

recreated:

cordova

erify the Signature🔗

on

Know more about UPI Intent and its benefits.

.

The event names are exposed via the constants EVENT_PAYMENT_SUCCESS and EVENT_PAYMENT_ERROR from the Razorpay class. Use the on(String event, Function handler) method on the Razorpay instance to attach event listeners. Attach Event ListenersCopy

t.

t.

s.

r app's pubspec.yaml

The error code is available as the code field of the PaymentFailureResponse instance passed to the callback.

.

Method

Method

Method

Method

Method

Method

Meth

Metho

plugin

A complete list of UPI supported apps and their package names is available here.

The sample code below will send collect request to gaurav.kumar@exampleupi handle.

In this case

In the case of

The sample code shown below allows the checkout to perform a netbanking transaction for a payment of ₹299.35:

In the case of

The sample code shown below allows the checkout to accept a card payment of ₹299.35:

In the case of

The Razorpay Flutter Custom SDK lets you integrate the supported payment methods on your Flutter app's Checkout form.

:

The Razorpay WooCommerce plugin is released under the General Public License v2.0 (GPLv2.0). Click here for details about the license. Check the license text in the license file on GitHub.

Handy Tip

it works🔗

If you are using WooCommerce with your WordPress site, we have a WooCommerce plugin too!

Razorpay Sub-Merchant Onboarding APIs are RESTful. All our responses are returned in JSON. You can use Razorpay APIs in two modes, Test and Live. The API key is different for each mode. To complete the onboarding process for the sub-merchant, check the KYC document requirements. You can try out our APIs on the Razorpay Postman Public Workspace.

Webhooks

Install via the WordPress Plugin Directory🔗

ebsite.

download the plugin from the WordPress plugin directory or install it manually.

Click here for details about the license.

The plugin has been tested using WooCommerce v4.8.

You need to make network calls to use this plugin. Ensure you have the php-cURL extension installed to make the required network calls.

:

If you are not using WooCommerce, you can use our native plugin for WordPress.

As per Apple's policy, if you are using a subscription model in your iOS app, you must use Apple's in-app purchase APIs. Apple does not allow to redirect out of the app for digital product purchase.

tOrders.

The error code is available as the code field of the PaymentFa

ExternalWalletResponse🔗

PaymentFailureResponse🔗

PaymentSuccessResponse🔗

Refer to our standard checkout documentation for a complete list of options for the checkout form.

Method🔗

Razorpay class🔗

Get Packages🔗

Learn more about Proguard rules.

Add Proguard Rules (Android Only)🔗

.

ml

1.2 Add the Dependencies🔗

Following is the latest version of our framework:

versions

RazorpayPaymentCompletionProtocolWithData🔗

RazorpayPaymentCompletionProtocol🔗

For example, the Swift call is:

Order is an important step in the payment process.

typealias Razorpay = RazorpayCheckout

Watch the GIF to see how to add Frameworks, Libraries and Embed Content.

-

In this case,

Given below is the sample code:

In this case, the SDK invokes an intent, which will be handled by the Cred app installed on the iOS device. Follow these steps:

-

.

For example, the sample code below will send a collect request to the gaurav.kumar@exampleupi handle.

In this case, it will send the collect request to the UPI app for the specified VPA. Add the following code to initiate a UPI collect request.

Pass the WKNavigationDelegate actions to the SDK🔗

at your Server-side🔗

formula:

alternate

from

using

Build Integration Test Integration Go Live Checklist

Support🔗

-

OpenCart Extension

Step 2: Configure OpenCart🔗

Install the Plugin🔗

.

Send the customer_id, and token_id(associated with the saved card) attributes along with cvv in the payment request:

-

do the following:

The below method fetches the card network for a card. A minimum of 6 digits is required to identify the network.

.

As per Apple's policy, if you use a subscription model in your iOS app, you must use Apple's in-app purchase APIs. Apple does not redirect out of the app for digital product purchases.

A module map is used to define the header files that should be converted into modules and used by your project. Razorpay handles this internally. You are facing this issue because we have assumed that your default Xcode's name is Xcode.app, which might not be the case always. For example, your default Xcode will appear as Xcode9.3. To resolve this issue, insert this script; in the directory that contains Razorpay.framework file and run it from your terminal, and you are good to go!

There are multiple Swift versions available, but unfortunately, Apple does not make all the versions compatible, so we release frameworks compiled in multiple Swift versions. Download the framework that is compatible with your project. If you run into a compatibility issue, ensure that you try both frameworks.

If you have or do not have bitcode enabled project, you can use our bitcode enabled framework. There will be no issue, and our bitcode enabled framework will work for both cases.

Please ensure that Razorpay.framework is present in your project settings in both the Embedded Binaries and Linked Frameworks. Also, set Always Embed Swift Libraries to "yes" in the project settings. It can happen because of the incompatibility between the developed Swift version with Razorpay.framework and the Swift version of your project. We recommend using the framework compiled with the required Swift language from our iOS documentation.

this message only when running the app on a simulator or using a test key to initialize the SDK.

Be rest assured, as you would see

We highly recommend that you always use the latest SDK.