India go-live checklist

Follow this checklist before you start accepting live payments in India.

If you want to process payments in India, follow the steps in the payments India compliance guide first.

Adyen automatically sets up your live Customer Area company and merchant account once all our KYC checks are complete. We follow the naming conventions of your test company account.

When your live India company account is available:

The payment methods configured on your test environment are available on live. The payment methods on your merchant accounts are the same as they are on test, with a new merchant ID (MID) for your India Customer Area.
Payouts to your bank account in India are set up.
Your admin user is the same as the admin user on the test environment. They receive an email asking them to verify that the setup is correct and to change their password.

The following steps show you how to configure your live India company account, and how to perform end-to-end tests.

Configure your live India Company Account

Set up your live account structure

Create additional merchant accounts if needed for your business.

Give team members access to the live environment

Create a separate user for each team member who needs to access your live India Customer Area.
Give each user the roles and account access required to perform their tasks.
Set up Customer Area notifications to be notified of important events such as chargebacks.
Set up two-factor authentication.

Finance

Receive payouts from Adyen

Add information about the bank accounts in India where you want to receive the payouts from Adyen, if you have not done so as part of your application.
Review and change how you get paid, if required.

Use reports for reconciliation

Set up automatic generation of reports.
Use the Settlement details report to reconcile your accounts on a transaction level.
Consider automating your reconciliation process.

(Optional) Set up a Reserve

Consider setting up a Reserve: this is used for refunds and other operational expenses in case of insufficient in-process funds.

Risk

Review and customize your risk profile.
Create block and trust lists (referrals) in your India company account.
Velocity risk rules will not work as well for your India company account at first, because they rely on historical transaction data.
Set up Customer Area notifications and webhooks to get notified when you receive a Notification of Fraud (NOF) or a Chargeback (NOC).
Make sure that you know how risk rules are triggered by the information that you send in your payment request. Some fields are strongly recommended to include because they are required for specific risk checks.

API communication

To make live API requests:

Generate an API key in your India company account, and copy this to your live integration.
Make sure that your live API credentials have the required API permissions.
Update the Adyen endpoints for your India accounts to your live endpoints. You can find the correct URLs in your India company account under Developers > API URLs.
If you have implemented Adyen front-end checkout solutions such as Drop-in, Components or a custom card component, set the environment value to live-in in your front-end configuration object and update the URLs to India-specific ones:
- https://checkoutshopper-live-in.adyen.com/checkoutshopper/sdk/[version]/adyen.js
- https://checkoutshopper-live-in.adyen.com/checkoutshopper/sdk/[version]/adyen.css
Your setup is working if the endpoints you are using correspond to the endpoints listed in your India company account and you can see payments listed in the Payments list in your Customer Area.

Set up payment methods

Contact our Support Team to add the payment methods that you want to offer to shoppers in India.
Make sure that payments appear correctly on the shopper's bank statement. Configure the shopperStatement field when making a payment or when creating a payment session.

Webhooks

Set up webhooks in your live India Customer Area.
Make sure that you acknowledge webhooks with a successful HTTP response status code, for example 200 in the response, to prevent webhooks from being queued.
Make sure that you receive all webhooks needed for your integration.

End-to-end testing

To make sure your integration can handle the entire payments lifecycle, you need to test possible scenarios with real payment details.

Payments with real details incur fees.

For each payment method that you offer, make a successful payment using real details.
Make a payment with resultCode: Refused, for example by entering incorrect card details.
Make a payment with refusalReason: FRAUD, by triggering multiple risk checks to achieve a risk score above 100.

Local payment methods

The local payment methods Wallets India, Online Banking India, PayTM Wallet and UPI require the shopper to be redirected or manually go to another website or app to complete the payment.

If you implemented any of these, test the following scenarios:

After being redirected, wait for more than five minutes to complete the payment.
Select the cancel or back button on the redirected page, to cancel the payment.
Close the browser when on the redirected page, to simulate the shopper abandoning the session.

Tokenization

If you process recurring payments with recurringProcessingmodelModel CardOnFile, UnscheduledCardOnFile or Subscription, implement the CardOnFile and recurring flows.

Refunds

Make a payment in your India company account, then refund it. Check that the authorisation and refund request are going through the India endpoints and company account.