With Adyen MarketPay, you can choose from the following sub-merchant onboarding options:
- Use our Hosted Onboarding Page where sub-merchants directly provide their information. This solution requires less implementation effort.
- Build your own onboarding implementation. Collect information from your sub-merchants and send it to Adyen over our API. You are in full control of the UI and user experience.
After we receive information from you or directly from your sub-merchant, we automatically conduct required verification.
Each sub-merchant will need to go through Know Your Customer (KYC). KYC is the process of a business (Adyen) identifying and verifying the identity of its clients (your sub-merchants). This is required by payment industry regulations.
We categorize the required information for verification into these check types:
Refer to Verification checks for required information per check and per country.
You also have the option to use your existing KYC process.
If the sub-merchant is unable to provide the information required for a given verification check within 30 days of its status change, the account holder's state will be updated to inactive and payment processing will be temporarily disabled.
A 6 week deadline is set from this point by which you need to provide the requested information. Once you provide the requested information, the account holder's state will be restored to active and processing will be enabled.
Not providing the information within this 6 week deadline will suspend the account holder. The payments that have not been paid out for this account holder will be refunded, and you will no longer be able to make API calls updating the account holder.
To unsuspend the account holder, use the /unSuspendAccountHolder endpoint. This updates the account holder's status to inactive, sets another 6 week deadline, and allows you to make API calls updating the account holder again.
Multiple verification attempts
It is possible your account holder might provide information several times for a given verification check without Adyen being able to validate them. In these cases, the verification check status will change to RETRY_LIMIT_REACHED.
Each check has its own means of resolving the RETRY_LIMIT_REACHED status. Refer to Verification check for each check and how to resolve RETRY_LIMIT_REACHED.
Failing to resolve the RETRY_LIMIT_REACHED will put the verification check under manual review.
Each verification check has an accompanying Verification status, which reflects where the account holder is in the verification process and whether more information is required.
Whenever a verification check is updated, you will receive an ACCOUNT_HOLDER_VERIFICATION notification specifying the check that was updated and its new status.
All account holder and account changes, including creation, notifications will be communicated to you via webhooks. Use our Notification Configuration API to configure your webhooks. You also can find a list of all notifications in Notifications.
Using your own KYC process
If you already have your own KYC process, you may be eligible to continue using it and we would not perform any validation on your account holders.
We will need to audit and approve your KYC process. Reach out to our Support Team if you are interested in using your existing KYC processes.
Once approved, you will still need to upload all the information of your account holders but we won't perform any validation.