Adyen Integration v2.0

Knowledge Center > Billing and Payments > Payment Gateways > Supported Payment Gateways > Adyen Gateway > Adyen Integration v2.0

Adyen Integration v2.0

This feature is in Limited Availability. We are actively soliciting feedback from a small set of early adopters before releasing as generally available.

Zuora partners with Adyen and provides a new Adyen gateway integration called Adyen Integration v2.0. This integration supports the Adyen's Checkout API v41 and Payment API v40, and the fields for Visa mandate and stored credentials.  

Supported Payment Methods and Payment Operations

The Adyen Integration v2.0 payment gateway integration supports the following payment methods and payment operations:

Supported Payment Method Payment Method Types Payment Operations
Credit Cards
  • Visa
  • MasterCard
  • Discover
  • American Express
  • JCB
  • Diners Club
  • China Union Pay
  • Validate
  • Payment
  • Refund
  • Credit
Credit Card Reference Transaction
  • Credit Cards
  • SEPA
  • Validate
  • Payment
  • Refund
  • Credit
Bank Transfer
  • SEPA
  • Payment
  • Refund
  • Credit

Stored Credential Transactions

Adyen Integration v2.0 includes support for the Visa Stored Credential Transaction framework.

Configure the Adyen Integration v2.0 Instance

Prerequisites

  • Generate an Adyen API Key for your merchant account. See How to get the API key for instructions on how to obtain the API key.
  • For Bank Transfer transactions, you must send a request to enable “Separate Direct Debit with authorization type AUTH” for your Adyen merchant account when setting up SEPA with Adyen.
  • You must obtain the live-URL prefix from your Adyen merchant account for production. This setting will be saved as a gateway setting in Zuora. Failure to specify this prefix will result in that requests cannot be processed in production.

Configuration

  1. Click your username at the top right and navigate to Settings > Payments > Setup Payment Gateway
  2. Select Adyen Integration v2.0 from the Gateway Type drop-down list.
  3. Click create gatewayAdyen v2.0 Configuration Page
  4. Complete the information for the gateway instance. See below for more information on the fields.
  5. Click save gateway information after entering the necessary information.

Common Configuration Fields

There are some common fields you must complete for every gateway configuration. Zuora recommends reviewing Zuora recommends reviewing Setting Up Payment Gateways for information on these fields: 

  • Type
  • Name
  • Use Gateway Test Environment
  • Merchant Account
  • Cards Accepted
  • Default Authorization Amount: Currently, the Adyen Gateway does not support customizing this field. The default value is 1.
  • Verify new payment method (required)
    The Shopper Reference token is required in the payment transactions. You must select the Verify new payment method check box in the configuration so that a Shopper Reference token is generated by Adyen during the payment method verification.
  • Verify updated payment method (optional)
  • Enable gateway reconciliation (Optional): Select to enable gateway reconciliation on this instance. The Gateway Reconciliation job for Adyen is scheduled to start at 11:00 pm (PST) every day. See Adyen Gateway Reconciliation for tips to consider when using gateway reconciliation. For more information about this option, see Gateway Reconciliation.
  • Reconciliation Username (Optional): The username needed to retrieve Adyen reports to perform gateway reconciliation. This field is required if you select the Enable gateway reconciliation check box.
  • Reconciliation Password (Optional): The password needed to retrieve Adyen reports to perform gateway reconciliation. This field is required if you select the Enable gateway reconciliation check box.

Specific Configuration Fields

The following fields are specific to Adyen Integration v2.0:

  • API Key: The API Key generated for your merchant account in Adyen.
  • Live URL Prefix: The live-URL prefix associated with your Adyen merchant account. This prefix is required to form the production Adyen endpoint. The format for the prefix is the combination of the [random ID] and [company name] from the live endpoint. For example, abc123-Zuora.

Credit Card Reference Transactions (Tokenization)

Zuora supports Adyen tokens. Tokens are used for credit card reference transactions in Zuora. A reference transaction is simply a representation of a credit card payment method without having sensitive payment method information like the credit card number stored in Zuora. The token cannot be used with another gateway, which is why Zuora recommends storing credit card information in Zuora whenever possible. 

Apart from credit card tokens, you can also add an existing Adyen SEPA token in Zuora. To use an existing token, enter the shopperReference token in the Token Id field when creating a credit card reference transactions payment method. Note that only the Token ID (shopperReference) is used to create a token. Second Token ID is not needed.

This feature is in Limited Availability. If you wish to have access to the feature, submit a request at Zuora Global Support

Limitations

  • Because payments are created with 0 capture delay, all payment transactions will be in the SentForSettle status. However, Adyen can only cancel the payments in the Authorised status that is prior to the SentForSettle status. Therefore, Zuora does not support the Cancel operation for all payment method types.
  • Validating the Bank Transfer payment method is not supported by Adyen.
  • Validating an existing mandate Id or using a mandate Id for payments are not supported by Adyen in the current version of the checkout API (version 41).
     

 

 

Last modified

Tags

Classifications

(not set)