Page tree
Skip to end of metadata
Go to start of metadata

Use the values in the tables below to configure the Adyen payment provider/authorizer with the described settings.

Note:

In addition to the EDGE configuration settings, be sure to also follow the instructions in the Adyen Account Settings tab.


(The procedures for accessing and configuring these settings are described in Add an Authorizer.)

Parameter

Value

Comments

AUTHORIZER NAME

Adyen

Can be any meaningful value.

AUTHORIZER CODE

Adyen

This value should exactly match the provider/ authorizer Bean implementation.
(Service Implementation Bean is a term used in Java Platform, Enterprise Edition, for a Java object implementing a Web service.)

Do not change if you are not sure.

SITE URL
Test: 

 Production:


https://ca-test.adyen.com/ca/ca/login.shtml

https://ca-live.adyen.com/ca/ca/login.shtml

The field must be populated, but the value is not currently used.
Any value is valid.
Suggest using specified values for consistency/clarity.

LOGIN URL
Test: 

 Production:


Not used

CUSTOM URL 1


Not used

START DATE

01/29/19

Effective date

END DATE

 

Ending date, as applicable. Can be empty.

STATUS

Active 

Should be "Active" for the current provider.
(Status of "New" is not recommended)

(The procedures for accessing and configuring these settings are described in Add Authorization Info.)

Parameter

Value

Comments

AUTHORIZER NAME

Adyen

Match the value in the Authorizer Name field in the Authorizer parameters.

AUTHORIZATION
INFO CODE

Adyen

Any meaningful value

USER NAME

Unique for each merchant

Adyen login user name

PASSWORD

********

Adyen login user name

EXTERNAL MERCHANT ID

Unique for each merchant,
value provided by
Adyen

Adyen merchant account code

TERMINALID


Not Used

PAYMENTECH BIN

 

Not Used

PAYMENT TOKENIZATION
ENABLED

Yes

Tokenization is supported.
Must be enabled (Yes).

DOES AUTHORIZER SUPPORT
MULTIPLE CAPTURE AGAINST
SINGLE AUTHORIZATION?

Yes/No

Supports multiple captures against a single authorization.

Can be enabled (Yes) or disabled (No), as applicable.

START DATE

01/29/19 

Effective date

END DATE

 

Ending date, as applicable. Can be empty.

CURRENCIES

By default, all available
currencies are supported

Select from list of available currencies, as applicable. If empty, all currencies are considered to be supported.

 ITEM TYPES

Select from a list of available catalog item types. (Optional)

With this parameter, authorizers can be set up to process payments using one or more specific catalog item types. Multiple authorization info configurations can be set up for one or more authorizers using different codes, each associated with a unique item type or item types. Order items can then be processed through the authorizer/authorizer code that is based on the item's corresponding type.

Item types are defined in EDGE System Admin>Catalog>Item Types.

 PAYMENT TYPES Credit Card Credit Card processing is supported. Must be selected.

DISABLE FRAUD DETECTION
FOR ORDER SOURCES


Not Used

STATUS

Active

Should be "Active" for the current provider.
(Status of "New" is not recommended)

(The procedures for accessing and configuring these settings are described in Configure Authorization Info Parameters.)

Parameter

Default Value

Comments

LiveEnvironmentFalse

Required parameter.

True = Live environment, False =  Test environment

URLPrefix

Required parameter.
Used only for live environment.

The URL prefix [random]-[company name] from the merchant's Adyen live Customer Area > API URLs and Response.

For more information, refer to Adyen Live Endpoints>Checkout endpoints in the Adyen documentation.

APIKey

Required parameter.
Merchant's API key from Adyen console's Customer Area.

For more information, refer to How to get the API key in the Adyen documentation.

DoNotProcessTransaction

No

Optional parameter.

For payment transactions that are for reporting purposes only. When "Yes," third parties that manage their own payments can send full transaction details upon order import so that EDGE can track the payments in an Order Details page or Payment Transactions report without actually processing any payments.

Valid values:

  • Yes - a payment transaction WILL NOT be processed
  • No (default value) - a payment transaction WILL be processed


In addition to the EDGE configuration, several actions need to be taken for the merchant's Adyen account:


For the merchant's Adyen account, the "Capture Delay" parameter in the Adyen console's Customer Area must be set to manual.

With manual capture, a capture is explicitly requested for each payment.

To set the "Capture Delay" parameter:

  1. Log into the Adyen console using your merchant account Username and Password.

  2. Switch to the applicable merchant account, if necessary.
  3. Select Account>Settings.



    The Manage Merchant Account <merchant name> page opens.

  4. Use the drop-down menu to select manual in the Capture Delay field.
  5. Click Submit.

Server communication settings need to be configured in the Adyen console for the merchant's account so notifications can be received.

To configure communication settings:

  1. Log into the Adyen console using your merchant account Username and Password.



  2. Switch to the applicable merchant account, if necessary.
  3. Select Account>Server communication.


    The Server communication settings for <merchant name> page opens.



  4. Click for Standard Notification. The Standard Notification page opens.



    1. Enter the applicable public services host URL in the URL field.
      The URL must use the following syntax: 
      .         https://{Services-URL}/payment/NotificationServer/{ProjectID}/jp.jws 
    2. Be sure that the following values are also entered, leaving the default values for all other fields:
      • SSL Version:  TLSv1.2
      • Service Version:  1
      • Active:  checked
      • Method:  JSON

    3. Click to save your values. The Server communication settings for <merchant name> page opens again with your configured values displayed at the top.

Contact the Adyen support team and request that the following be set up for the merchant's Adyen account:

SettingComments
Set up "API PCI Payments role" to enable raw card data collection/submissionRequired when EDGE applications – Agile and the Customer Service Portal (CSP) – are the source of the order.
Set up "rechargeSynchronousStoreDetails" account data property to enable synchronous tokensRequired when EDGE applications – Agile and the Customer Service Portal (CSP) – are the source of the order and when tokenization is enabled.
Set up "allowMultiplePartialCapture" account data property to enable multiple partial captures

Required when multiple capture is enabled.






  • No labels