Onboarding v4

This page provides an overview of the changes in onboarding v4. For more information about onboarding versioning, see here.

• Limitations on using PO box as address
• Improvements for LEM API
• Improved validation for ID document uploads
• New validations on fields
• Onboarding underage users
• Onboarding unincorporated partnerships
• Providing registration number before first payment
• Requirement for doing business as name
• Requirement for principal place of business
• Requirements for specific countries/regions
• Support phone number and phone from users
• Updates for hosted onboarding

Changes in v4 for financial products

• Requirement for business lines and industry codes for issuing
• Source of funds for issuing and business accounts

Limitations on using a PO Box as an address

• An individual user cannot use a PO box as their residential address.

• An organization can use a PO box as their registered address. However, they must also provide an alternative address for their principal place of business. The address for the principal place of business cannot be a PO box.

You can test your error handling flow for the new verification error messages.

Improvements for Legal Entity Management API

When you delete a document by making a DELETE /documents/{id} request, it now returns a 404 response.

Improved validation for ID document uploads

We added a validation error when a low-quality ID document, such as a passport or driver's license, is uploaded by making a POST /documents. This allows you to quickly see if an improved document needs to be uploaded to pass verification checks.

New validations on fields

To meet compliance requirements, we have added validations to specific fields for legal entities and legal arrangements. These validations are applicable for both hosted onboarding and API-only onboarding.

Onboarding underage users

Users between the ages of 13-18 in particular countries/regions can be onboarded with a legal representative. See here for more information.

Onboarding unincorporated partnerships

Beginning with onboarding v3, you can now onboard unincorporated partnerships in selected countries/regions. Unincorporated partnerships can only be onboarded using the Legal Entity Management API.

Providing registration number before processing payments

Organizations must provide their registration number prior to processing payments. See here for the accepted format per country.

Requirements for doing business as name

Adyen must identify if the name that an organization or legal arrangement trades under is different from its registered name. This is referred to as the Doing Business As (DBA) name. Organizations and legal arrangements that do not have a DBA name can indicate this while onboarding.

If you are using hosted onboarding, users can select this in the hosted onboarding page. If you are using the LEM API, set the corresponding value to true in your POST /legalEntities request:

• organization.doingBusinessAsAbsent
• soleProprietorship.doingBusinessAsAbsent
• trust.doingBusinessAsAbsent
• unincorporatedPartnership.doingBusinessAsAbsent

Make sure that your systems can handle all the related verification error messages.

Requirements for principal place of business

If an organization has a principal place of business address, the country must be the same country as its registered address.

Make sure that your systems can handle all the related verification error messages.

Requirements for specific countries/regions

The following compliance requirements are based on the country of the user and its associated entities.

Support email and phone numbers

If you are a platform model, your users must provide both a support phone number and email address.

• If your user is a sole proprietorship, they need to provide this information in the individual legal entity of the owner of the sole proprietorship.

• If your user is a trust, they need to provide this information in the individual or organization legal entity of the main trustee.

• If your user is an unincorporated partnership, they need to provide this information in the individual legal entity of the main partner.

• If you are using hosted onboarding, users can add this information in the hosted onboarding page.

To use the Legal Entity Management API, in your POST /legalEntities request, specify the required fields:

• individual.support.phone
  • individual.support.phone.number
  • individual.support.phone.type
• individual.support.email

or

• organization.support.phone
  • organization.support.phone.number
  • organization.support.phone.type
• organization.support.email

Make sure that your systems can handle all the related verification error messages.

Updates for hosted onboarding

Publicly listed companies can now provide their ticker symbol in the hosted onboarding page

Make sure that your systems can handle all the related verification error messages.

Requirement for business lines and industry codes for issuing

To issue cards to your users, you must create business lines for them. To submit this information to Adyen, make a POST /businessLines request, specifying the service as issuing. In your request, specify the industry code.

Make sure that your systems can handle all the related verification error messages.

Source of funds for business accounts and issuing

Adyen is required to verify the source of funds (SOF) used to fund an account. This requirement is applicable for both card issuing and business accounts.

Depending on the type of funds, we may request additional documents as proof. We strongly recommend that you have these documents available before starting in order to speed up this process.

To submit this information to Adyen, make a POST /businessLines request, specifying the service as either:

• banking for business accounts
• issuing for card issuing

If the source of funds was processed through Adyen, set the sourceOfFunds.adyenProcessedFunds to true. If the source of funds was not processed through Adyen, set the sourceOfFunds.adyenProcessedFunds to false. You must then include the sourceOfFunds.type and sourceOfFunds.description. The description must state the origin of the source of funds.

The following table shows the accepted funding sources and the required documents for each type, if requested. If the type of accepted document has a listed date requirement, the document must meet this requirement.

Make sure that your systems can handle all the related verification error messages.