On this page, you can find all changes in the new Platforms integrations and financial products, such as Issuing. For an overview of the changes in a specific area of your integration, you can filter the release notes by category, version, and release date.
Platforms and financial products
Get updates by RSS
Filter by
Copy url
Onboarding
Removed
You can no longer update the KYC details linked to the legal entity of your liable account holder using the Customer Area or hosted onboarding. To update the details, reach out to our Support Team.
Copy url
Onboarding
New
Marketplaces and platforms can now onboard users in New Zealand.
Copy url
Onboarding v3
New
We have implemented a new onboarding flow for users under the age of 18 years old. Note that users younger than 13 can never be onboarded.
Depending on their country of residency, users between the ages of 13 and 18 can be onboarded with a legal representative, such as a parent or guardian. The legal entity ID of the minor user must be updated with an entity association specifying the relationship.
To use this feature, reach out to your Adyen contact.
Copy url
Onboarding
New
If you have an Adyen for Platforms integration, you can now onboard individual, organization, and sole proprietorship legal entities in Hong Kong.
Copy url
Onboarding v3
This summarizes the most important changes in Onboarding v3, which includes both the Legal Entity Management API and Hosted Onboarding
Improved
Improved information and validations for transfer instrument creation
When creating a transfer instrument in v1 and v2, the bankAccount object does not specify the required information required for accounts based on the country and currency combination.
We added the type field. This field specifies, for example, the bank account is a local account in the United States, and the required information based on that type.
For a US bank account, set the type to usLocal. When the type is usLocal, the fields accountNumber and routingNumber are required. For UK bank accounts, the type is ukLocal and the required fields are accountNumber and sortCode.
In LEM v3, the currencyCode has been removed from the bank account object since it is not needed to create a transfer instrument. If you need to block the creation of cross-border transfer instruments, you can use the countryCode of the transfer instrument and the country of the associated legal entity.
New
Support for multiple transfer instruments
The capability sendToTransferInstrument is now validated at both the transfer instrument resource and associated legal entity level. Previously, this capability was only validated at the legal entity level, which prevented payouts for users with multiple bank accounts that were not all verified. The verificationStatus of the capability and any verfificationErrors are returned:
- by making a GET /transferInstruments/id request.
- by listening to balancePlatform.accountHolder.updated webhooks.
Compliance requirements for Onboarding v3
| Description | Details |
|---|
| Description | Details | |
|---|---|---|
| Data review | Adyen may occasionally require your users to review and confirm that their data is up-to-date. | |
| Required information and verification checks | The following requirements are enforced during the verification process.
|
|
| Requirements in APAC countries |
|
|
| Terms of Service and PCI | If you are using custom onboarding, confirm that your user has accepted the Terms of Service or signed self-assessment questionnaires. | |
| Business lines | Payment facilitators need to create business lines when onboarding users. |
Verification deadlines and data reviews
When a user updated their data in LEM v1 and v2, their capabilities were disallowed until verification checks were completed. We now provide a verification deadline. They are allowed to continue using the capabilities while the deadline is active.
We now inform you when your user needs to review their data by sending a verification error "Review of data is required" in a webhook. There is a verification deadline to review their data and they are allowed to continue using their capabilities while the deadline is active. To resolve the error, make a POST /legalEntities/{id}/confirmDataReview request to confirm the user has reviewed their data.
Terms of Service and PCI requirements
Adyen now determines if your users need to accept the Terms of Service and sign self-assessment questionnaires to comply with Payment Card Industry Data Security Standards (PCI DSS).
If you are using hosted onboarding, these steps are included in the user's hosted onboarding page. For custom onboarding, listen to webhooks and follow the steps to have your user accept the Terms of Service or sign self-assessment questionnaires.
Changed
Aligning business lines with Adyen products and services
We replaced the capability field with the service field. The capability field is now deprecated. The possible values for service are:
-paymentProcessing: corresponds to capability receivePayments.
-banking corresponds to capability issueBankAccount.
Note that you still must request capabilities for your account holders.
Error responses for legal entities
In the /legalEntities responses for POST, PATCH, and GET, we separated the status of capabilities from the problems that you need to resolve. We also grouped together the problems per type of capability.
We also added a new endpoint /legalEntities/{id}/checkVerificationErrors returns only the verificationErrors for a legal entity in the response without any additional details.