Integrating Adyen With Chargent In Salesforce

Before you start integrating the Adyen gateway in Chargent with Salesforce, make sure you have completed the following steps.

Before setting up your gateway, install the latest version of Chargent and configure your user permissions. Guides for these topics are available below to help you get started.

• Installing and Updating Chargent
• License Assignment (Production Only, not required for Sandbox)
• Permission Assignment

In order to process live payments with Adyen, you must complete the following steps:

• Set up and maintain a proxy server to manage authentication. See Setting Up Your Proxy Server.
• Prove to Adyen that you are PCI compliant based on their requirements. See Enabling the API PCI Role in Adyen.

Contact Sales to start a discussion about your Adyen to Salesforce connection requirements. Test environments do not require the above specifications.

Before installing Chargent in production, we highly recommend installing and testing in a Salesforce sandbox. The following topics provide instructions for obtaining your test gateway credentials and creating a test gateway record in Salesforce. Remember to refresh your sandbox beforehand to ensure that your sandbox is aligned with your production configurations.

If you don’t already have Adyen credentials for testing, you must set up a Test Account. Obtain your Adyen Test Account by signing up at https://www.adyen.com/signup.

After creating your Adyen Test Account, Adyen will send an email with your Account and Username credentials alongside a link to set your password.

There are a few settings that must be enabled after creating your Adyen account prior to setting up your gateway integration in Salesforce.

Request the enablement of the API PCI Payments feature from Adyen. Adyen’s support team should have no problem enabling it for test accounts. However, live accounts will require proof of PCI Compliance before the API PCI feature can be activated.

To Request access to the API PCI feature, log in to your Adyen account and submit a support ticket.

If you plan to use tokenization, you must enable the Recurring Details checkbox in your Adyen account. Tokenization helps you reduce the scope of your PCI compliance and improve security. We recommend all customers enable tokenization.

1. Log in to your Adyen account and click Developers in the left sidebar.
2. Click Additional Data Settings.
3. Under the ‘Payment’ header, check the checkbox for Recurring Details.
4. Click Save Configuration.

If you do not enable tokenization in Adyen, a token will not be returned to Salesforce, and tokenization will not function properly.

To verify your test gateway credentials in Salesforce, Chargent requires the following gateway information:

• Account
• API Key
• Client Key
• Environment

Log in to your Adyen account and follow the instructions below to find and save the required credentials.

The Account credential effectively represents your Adyen ‘Merchant Account’. You can find this credential by following these steps.

1. Click Settings on the left sidebar.
2. Click Merchant accounts.
3. Copy the ‘Account Code’ for the ‘Merchant Account’ you plan to use.

Your API Key and Client Key are found on the same page. Follow these steps to generate and save your keys:

1. Click Developers on the left sidebar.
2. Click API Credentials.
3. Click on your username (‘ws’ in the example below).

4. Under Server Settings > Authentication, copy and save the API Key. Click Generate New API Key if no key is present.
   • You can only copy the API Key once after it is generated, so ensure you save the key in a secure location. You can generate a new key at any time, but ensure all systems that utilize the key are updated appropriately.

6. Scroll down to the Client Settings > Authentication and copy and save the Client Key. Click Generate Client Key if no key is present.

7. Click Save Changes.

Now that you have your Account, API Key, and Client Key credentials, all that is left is the Environment credential. For test environments, the value for the Environment credential is simply ‘test’.

With your credentials in hand, it’s time to create a gateway record in Chargent and verify your Adyen Test Account credentials.

1. Login to your Salesforce sandbox (partial, full, or developer sandboxes work).
2. Go to the App Launcher and click the Chargent app.
3. Click the Chargent Settings tab and choose the Setup Wizard subtab.
4. Click Yes when prompted, “Do you have a Payment Gateway account?”.
5. Select ‘Adyen’ from the list and click Continue.

6. Enter your Adyen Test Account credentials, leaving the Endpoint Override field blank.
7. Choose a Gateway Currency from the picklist If your gateway requires a specific currency for authentication.
8. Check the Always request Strong Customer Authentication (SCA) checkbox based on your requirements.
   • When enabled, this setting ensures that Strong Customer Authentication (SCA) is explicitly requested for every transaction. This may result in issuers requiring additional authentication from the shopper, depending on their policies. Disable this option if you want to reduce the likelihood of unnecessary authentication challenges for transactions in regions where SCA is not typically enforced, such as the US.
9. Click Sign In.
10. When you receive a message stating “Your credentials have been successfully verified!”, click Continue to complete the steps in the wizard.
    • If you receive an error message in red, see the Checking Your Remote Site Settings section below or check out our troubleshooting tips.

The remaining choices in the Gateway Setup Wizard are determined by your specific use case. For more detailed information about the steps, see Gateway Setup Wizard.

The remote sites for your gateway should automatically activate when completing the Gateway Setup Wizard using the steps in the previous section. If you encounter any issues connecting to Chargent using your gateway credentials, ensure they have been correctly activated in your org.

1. Click the gear icon at the top right and choose Setup.
2. Enter “remote” in the Quick Find box and choose Remote Site Settings.
3. Locate the following Remote Site names and make sure the “Active” box is selected:

• • AdyenCheckout_Test
  • AdyenPalURL_Test

4. If the “Active” box is not selected, click Edit, select Active, and click Save.

Setting up your direct debit network is optional but recommended. When you reach the gateway setup wizard page labeled “Select the Payment Methods you accept,” select the direct debit network for your region.

Our Adyen integration supports the ‘ACH – US’ and ‘SEPA – Europe’ direct debit networks. Choosing the correct direct debit network allows you to accept bank account payments and display the correct direct debit network fields in Chargent.

Once you’ve tested your gateway integration in a Salesforce sandbox, you’re ready to move to production. See Moving from Sandbox to Production to learn how to migrate your Chargent configuration changes to your production environment. After moving Chargent to production, see Testing in Production for best practices prior to going live.

The Adyen sandbox and production accounts are entirely separate, so make sure any settings in sandbox are reapplied in your production environment.

If you have not applied for a Adyen production account, you can sign up here.

Customers who purchase Chargent intending to use the Adyen gateway integration will require internal expertise to develop and maintain a proxy server long-term.

Adyen doesn’t support OAuth 2.0, requiring the creation of a proxy server to act as middleware between the user/password authenticated Adyen notifications and the OAuth 2.0 authenticated chargent endpoint. The proxy server must be set up and maintained by individuals in your organization. Chargent is unable to assist with the creation of your proxy server.

We can, however, provide sample code to use as a starting point when developing your proxy server. We do not guarantee or warranty this code as it runs off the Salesforce platform. However, it is a secure web application implementing best practices, and the readme includes production deployment guidance. To access this solution, you must sign a free software usage agreement. For more information, please contact our Support Team.

So far, you’ve used your test Adyen credentials and created a test gateway in your Sandbox. Now, it’s time to create a new gateway record in your production environment specifically for processing live transactions.

1. Log in to your production Salesforce org.
2. Go to the App Launcher    and click the Chargent app.
3. Click the Chargent Settings tab and choose the Setup Wizard subtab.
4. Click Yes when prompted, “Do you have a Payment Gateway account?”.
5. Select ‘Adyen’ from the list and click Continue.
6. Click Live Transactions and enter your new live gateway credentials, leaving the Endpoint Override field blank.

7. Enter your Hostname. It will be [[random-companyName]] on the endpoint URL.
8. Choose a Gateway Currency from the picklist If your gateway requires a specific currency for authentication.
9. Check the Always request Strong Customer Authentication (SCA) checkbox based on your requirements.
   • When enabled, this setting ensures that Strong Customer Authentication (SCA) is explicitly requested for every transaction. This may result in issuers requiring additional authentication from the shopper, depending on their policies. Disable this option if you want to reduce the likelihood of unnecessary authentication challenges for transactions in regions where SCA is not typically enforced, such as the US.
10. Click Sign In.
11. When you receive a message stating “Your credentials have been successfully verified!”, click Continue to complete the steps in the wizard.
    • If you receive an error message in red, see our troubleshooting tips.

For more detailed information about these steps, see our documentation for the Gateway Setup Wizard.

With your live gateway record created, you are ready for the final phase of testing: running live transactions in a production environment. Visit Testing in Production for considerations and best practices related to testing in your production environment.

When testing with live payment information, you can prevent transactions from settling by voiding them immediately afterward. For more information, see Refunding and Voiding Transactions. As a precaution, we recommend using very low amounts to minimize any impact in the event you forget to void them.

To test gateway responses in the live environment, submit live transactions with the correct street address, zip code, and CVC information to generate successful responses. Likewise, submit incorrect street address, zip code, and card code information to generate other responses. You can void successful transactions immediately to prevent live test transactions from being processed.

Congratulations! You have successfully integrated Salesforce and Adyen! You can now process transactions through Adyen directly in Salesforce using Chargent!

All of Chargent’s gateway integrations support most of Chargent’s core features. Some features are reliant on support by the gateway itself. Chargent’s integration with Adyen includes, but is not limited to, the following features:

Using Adyen, you can validate US bank accounts on the Automated Clearing House (ACH) network via our partner, Lyons, a leading data verification provider. This feature is designed to satisfy NACHA’s mandate—Supplementing Fraud Detection Standards for Web Debits.

For more information, see ACH Validation.

Chargent’s integration with Adyen supports Address Verification System (AVS), a technology used to prevent fraud by validating the ownership of a credit card using the billing address of a credit card and matching it with the data on file at the credit card issuing company.

Your AVS results are stored in Salesforce using the AVS Response Code field on your transaction record. For definitions, see Adyen’s AVS Responses.

For more information, see Address Verification System (AVS).

Chargent’s integration with Adyen supports several currencies. Review Adyen’s Supported Currencies for more details.

Additionally, this gateway integration supports Salesforce’s Multiple Currencies feature.

For more information about currencies in Chargent, see Understanding Currencies.

Data levels allow you to send more information with each transaction, ensuring the security and authenticity of the payment. Higher data levels translate to higher savings on transaction fees. The following levels of data are supported by Adyen using Chargent:

• Level I
• Level II
• Level III

Learn more about the field mapping for Level II and Level III data.

For more information about data levels, see Understanding Data Levels.

Below, we’ve listed the payment method types that are supported when using the Adyen gateway integration. For more information about payment methods supported by Chargent, see Payment Methods Supported.

Credit Cards

• Visa
• Mastercard
• Discover
• American Express
• MC Eurocard
• UK Maestro
• JCB Card
• Diners Club

For more information, see Understanding Credit Card Payments.

Bank Accounts

• ACH – US
• SEPA – Europe

For more information, see Understanding Bank Account Payments.

Strong Customer Authentication (SCA) is a two-factor authentication (2FA) requirement wherein, during a consumer-initiated transaction, the cardholder must provide two of the three elements: something the cardholder knows, something the cardholder owns, something the cardholder is.

With SCA enabled, a pop-up window will appear when your customers make a payment via Payment Request or Take Payment, asking them to authenticate with 2FA, adding an additional layer of security to your customer-initiated transactions.

Learn more by visiting Strong Customer Authentication (SCA).

Our Adyen integration ensures that SCA is explicitly submitted for every transaction by default. As a result, issuers may require additional authentication from your customers, depending on various policies.

Chargent versions 7.80 and later allow you to disable this option in the Setup Wizard and instead use Adyen’s SCA settings, including the Dynamic 3D Secure feature. This reduces the likelihood of unnecessary authentication challenges for transactions in regions where SCA is not typically enforced, such as the US.

For more information, see Understanding Adyen’s SCA Setting in Chargent.

Tokenization allows you to store payment information at your gateway and not in Salesforce. Tokenization helps you decrease the scope of your PCI compliance and improve security by storing your customers’ payment information on Adyen’s servers and not in Salesforce.

To use tokenization, you must enable Recurring Details in Adyen.

Chargent’s Adyen integration supports tokenization for the following payment method types:

• Credit Card
• Bank Account

The token returned by Adyen is stored in the Token field on the Chargent Order and Tokenization on the Transaction records in Salesforce. Additionally, tokens are stored in a Chargent Tokens record when Payment Methods is enabled in your org.

To learn more about why we recommend tokenization, visit Salesforce Tokenization.

Chargent’s integration with Adyen supports the following transaction types:

• Authorize
• Capture
• Partial Capture
• Refund
• Partial Refund
• Credit
• Unlinked Refund

For more information about Transaction Types, see Understanding Payments.

Salesforce sends payment information to your gateway based on the field values in your Chargent Order records. Adyen stores the payment information in your Adyen account under Transactions > Payments. Then, the gateway sends a response to Salesforce, storing it in a Transaction record. We’ve listed a few important examples of how the data is mapped between Salesforce and Adyen below.

*If you do not enable Recurring Details in Adyen, the API will not return a value to the Tokenization field in Salesforce.

**The Invoice Number allows you to send custom invoicing or additional information about your transaction. Chargent does not automatically populate this field.

These Level II and Level III fields can increase the security and authenticity of your transactions. For more information about what data levels our Adyen integration supports, see Data Levels.

The Reason Code field on a Transaction record stores a response code provided by Adyen. To learn more about a specific response code, see Error Codes and Messages.

To review gateway responses in Salesforce, go to the transaction record in Chargent and examine these field values:

If you are having trouble connecting to your gateway, we recommend starting with these troubleshooting steps.

For additional troubleshooting tips or frequently asked questions about Adyen, check out Chargent’s knowledge base articles.

Please see contact Adyen for support related to your Adyen Account.

Contact our support team if you encounter any issues related to Chargent.

Chargent Quick Start Guide
Gateway Setup Overview
Supported Gateways