The setup from your test environment is not copied over to your live environment, so you need to configure live settings for:
If you want to offer your shoppers the option to pay with wallets, there are additional steps to take.
After you have configured your live Customer Area, test your integration by making real payments.
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 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.
- Consider setting up two-factor authentication for increased security.
Set up payment methods
The package renders the payment methods based on what is enabled in your Customer Area.
- Add all the payment methods that you want to offer to your shoppers.
- Check that the payment methods are rendered in the correct order in your checkout. You can change the order of local payment methods in your Customer Area > Settings > Checkout settings.
- Make sure that payments appear correctly on the shopper's bank statement. To make any adjustments to the shopper statement, contact our Support Team.
Finance
Receive payouts from Adyen
-
Add information about the bank accounts where you want to receive the payouts from Adyen, if you haven't 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 and compliance
Risk webinar
To learn more about risk management with Adyen, sign up for an upcoming webinar.
By default, your Adyen account has a risk profile based on industry standards.
- Review and customize your risk profile.
- Set up Customer Area notifications about Fraudulent Payments (NOF) and Chargebacks (NOC).
- Make sure that you know how risk rules are triggered, for example by making a payment where the billing address is different from the delivery address, or using different email addresses with the same IP address.
3D Secure
Note that for Visa and Mastercard, the enrollment for 3D Secure can take up to seven days. This means that you might not be able to offer 3D Secure to your shoppers immediately after your live Customer Area has been activated.
To render the 3D Secure 2 component in the live environment, implement your Content Security Policy (CSP) by authorizing scripts in your Retail React App.
We recommend that you learn the implications of implementing a Content Security Policy (CSP) to manage scripts for PCI DSS v4.0.
Depending on your integration, loading the 3D Secure 2 interface might require you to add more URLs for access control servers to your CSP. Adyen does not maintain a list of all URLs.
In the ssr.js
file of your Retail React App, add the script URLs for each payment method in a script-src
array. Refer to the ssr.js
file in our GitHubto see an example.
Compliance
When using our Salesforce Commerce Cloud package, you need to assess your PCI DSS compliance according to the Self-Assessment Questionnaire A (SAQ A).
API communication
Make sure that your live API credentials have the following permissions:
- Merchant Recurring role
- Checkout webservice role
- Checkout encrypted cardholder data
In your MRT environment:
- Replace the YOUR_SITE_ID_ADYEN_API_KEY value with the API Key from your live Customer Area.
- Switch the YOUR_SITE_ID_ADYEN_ENVIRONMENT value from TEST to LIVE.
Webhooks
-
Set up webhooks in your live Customer Area.
-
Check that you are receiving all webhook event types needed for your integration.
-
To prevent webhook events being queued, make sure that you accept all webhook events.
-
The package has a scheduled job that handles the webhook event. To test that this is working correctly:
- In your Customer Area, go to Developers > Webhooks.
- Next to Standard Webhook, select the edit webhook icon .
- Select Test Configuration.
- If you are on a company account, select a Merchant account from the dropdown list.
- In the Event dropdown list, select the event code.
If the webhook is working correctly, you will see a successful HTTP response status code, for example ResponseCode
: 200.
After setting up webhooks in your Live Customer Area, you need to update the following variables in your MRT environment with your live credentials:
- YOUR_SITE_ID_ADYEN_WEBHOOK_USER
- YOUR_SITE_ID_ADYEN_WEBHOOK_PASSWORD
- YOUR_SITE_ID_ADYEN_HMAC_KEY
Live environment region and URL prefix
- In your MRT environment:
- Update the YOUR_SITE_ID_ADYEN_ENVIRONMENT value with the
environment
value for the live endpoint region you want to use. - Get your live URL prefix and add it to the YOUR_SITE_ID_ADYEN_LIVE_URL_PREFIX variable.
- If you want to use different live endpoint regions for different sites, create new variables for your sites.
For example, for your two sites, RefArch and RefArchGlobal, create a RefArchGlobal_ADYEN_ENVIRONMENT variable and connect that site to a different region by setting the variable to theenvironment
value for the live endpoint region you want to use.
- Update the YOUR_SITE_ID_ADYEN_ENVIRONMENT value with the
Wallet payment methods
- If you use PayPal, follow the steps to set up your PayPal account, and add your live PayPal Merchant ID to your Customer Area.
- If you use Google Pay, follow the steps to go live with Google Pay.
- If you use Apple Pay, follow the steps to go live with Apple Pay.
End-to-end testing
To make sure your integration can handle the entire payment lifecycle with real payment details, you need to test possible scenarios with real payment details.
Payments with real details incur fees. To have enough funds available for refunds, consider setting up a Reserve.
- 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. - Make a refund using our API, including a partial refund.
3D Secure
- Make a successful payment with 3D Secure authentication.
- Make a 3D Secure payment where the shopper fails to complete the challenge.
Next steps
Once you have completed the above checklist, you are ready to accept live payments!