This article provides a comprehensive overview of the payment service provider Adyen as well as detailed instructions on how to configure and use its functions with collana pay.
Adyen is a payment service provider that specializes in payment processing. It is headquartered in the Netherlands. Various payment methods are accepted via the payment service provider.
This overview shows all payment methods currently available via Adyen and collana pay.
The following section contains the information required to connect collana pay with Adyen.
Settings in Adyen that need to be made by the customer
Step 1:
ApiKey: The authentication token is used to control access to certain functions or resources. This ApiKey allows collana pay to communicate with Adyen. Here we explain how an ApiKey can be generated.
- 1.1 Login
- 1.2. New credentials must be generated. The user name is generated automatically. The "Description" field can be entered as required. It is advisable to enter a unique identifier such as "collana pay Sandbox".
- 1.3 After the credentials have been saved, the following page opens:
An API key has been generated. This API key is required to set up the provider accounts in collana pay.
❗ The settings can now be saved by clicking the button "Save changes".
It is important to keep these API credentials secure and not make them publicly available, as they provide access to the payment functionality of the Adyen account. Developers and businesses use these credentials to process payments, manage chargebacks, generate reports and perform other actions via the Adyen API.
ClientKey:
- Generate ClientKey according to instructions. Only for payment methods such as Moto.
- add the following domain in the "Add allowed origins" step:
- Sandbox-V2: https://sandbox.collanapay.com
- PRD-V2: https://live.collanapay.com
Step 2:
MerchantID: This setting is required to clearly identify the identity of a merchant or company in a payment system. If different merchant accounts are used for different country/currency combinations, these must be stored. Here is how to create an account structure.
Open your Adyen account and navigate to Settings -> Merchant Accounts -> Request new merchant account:
The account created can be found in the "Merchant Accounts" overview.
Step 3:
Webhooks can be set up both at company level and at merchant account level. We recommend setting up at company level, as the setup then only needs to be made once.
The notification in the customer account must be set up to communicate with the endpoints. This setup is done via Webhook.
This explains how to make the settings.
- 3.1 enter collana pay end points
To do this, a new webhook must be created in Adyen Backend under Developer -> Webhooks:The standard webhook must always be chosen:
General
1. Description: It is recommended to write a description that makes it clear later on that it is about a webhook in connection with collana pay.
2. Server configuration: The link provided by collana pay is to be inserted here.
- Sandbox-V2: https://sandbox.collanapay.com/v2/notifications/adyen/
- PRD-V2: https://live.collanapay.com/v2/notifications/adyen/
3. Events: It is recommended to leave the setting to "Default events enabled".
Security
1. Username: These fields can be assigned as desired.
2: Password: These fields can be assigned as desired.
3. HMAC Key: Generate (NotificationsHmacKey) and notify collana hive.
❗Click on "Save changes" at the bottom right.
NotificationsAuthenticationUserName:
After the MerchantID has been created, a webhook is automatically created in the webhook overview based on the assigned description.
NotificationsAuthenticationPassword:
NotificationsHmacKey: These settings are made as in step 3. The Hmac key (Hash-based Message Authentication Code) is used to sign the API requests. It is used together with the API key to ensure that the data has not been manipulated during transmission and that the request originates from an authorized sender.
Important for the production environment and for some payment methods
- CheckoutUri: individual live endpoint (not required for import) [programmed on v66 or v69 for MOTO].
- ApiUri: individual live endpoint only relevant in the production system (programmed on v64).