Quick answer. An Adyen verification deadline is the last date by which an account holder on Adyen for Platforms must fix open verification errors before Adyen disallows the capabilities tied to them. Adyen sets a standard 30-day period for capabilities that move money out, such as sending funds to a bank account, and a standard 60-day period for capabilities such as receiving payments and issuing cards. The account holder keeps using every capability while the deadline runs. When the date passes with the errors still open, payouts or payments stop until verification clears.
Adyen verification problems rarely come from a fake business. They come from one field Adyen could not match, such as a legal name that differs by one word from the registration, an owner who left and was never removed, or a bank letter in the founder’s personal name. We read the exact error code before gathering a single document, because the code names the field that failed and often the fix Adyen expects.
What the Adyen Verification Deadline Means for Your Capabilities
Adyen for Platforms is the Adyen product used by marketplaces and software platforms that onboard sellers or service providers and pay them out. Each seller is an account holder linked to a legal entity. The platform collects that entity’s details, often through Adyen hosted onboarding, and Adyen runs KYC checks on the entity, its owners, its signatories and the bank account that receives payouts.
Each thing an account holder can do is a capability. Adyen’s capabilities documentation describes four verification statuses for every capability.
- pending. Verification is in progress. A first-time request stays at allowed false until checks finish.
- valid. Verification succeeded and Adyen sets allowed to true.
- invalid. Verification failed, for example because information is wrong or a document is missing. When verified data later changes or goes missing, the status reverts to invalid, yet the account holder keeps allowed true while a deadline is active.
- rejected. Adyen finished verification and the account holder does not meet the requirements. Adyen describes this status as final. Updating data or uploading documents cannot fix it.
A capability works only when two settings are both true. The allowed setting belongs to Adyen and reflects verification. The enabled setting belongs to the platform, which can switch a capability off without triggering any checks. A seller who sees payouts disabled after verification should ask the platform which of the two settings changed, because the fix is different for each.
The three events that start a deadline
Adyen’s verification overview lists the moments when new checks run and a deadline can be set.
- A data change after capabilities were granted. Adyen verifies the data again whenever the account holder changes it. A new director, a new address or a new payout account each triggers fresh checks. If they fail, Adyen may set a deadline.
- A periodic data review. Adyen occasionally requires account holders to confirm their data is current. Checks run at once on the existing record, including ultimate beneficial owners (UBOs) and signatories.
- A contractual obligation. Accepting a new version of the Terms of Service is one example Adyen names. The matching remediating action code is 2_902, Accept TOS. Our guide on suspension after unconfirmed terms covers that branch in depth.
Adyen also states that verification deadlines exist only in versions 3 and 4 of the Legal Entity Management API. A platform still on an older integration handles failed checks differently, so the account holder may never see a dated countdown at all.
Which Capabilities Get 30 Days and Which Get 60
The deadline length depends on the capability, not on the account holder or the type of error. Adyen publishes a standard table, and the split matters more than most sellers realize. Payouts sit in the shorter group.
| Standard deadline | Capability (API name) | What the account holder loses when it lapses |
|---|---|---|
| 30 days | sendToTransferInstrument | Payouts to the linked bank account |
| 30 days | sendToBalanceAccount | Moving funds to other balance accounts |
| 30 days | receiveFromTransferInstrument | Topping up from a bank account |
| 30 days | sendToThirdParty | Sending funds to third-party bank accounts |
| 30 days | issueBankAccount, getGrantOffers, receiveGrants | Business accounts and capital offers |
| 60 days | receivePayments | Accepting payments from customers |
| 60 days | receiveFromPlatformPayments, receiveFromBalanceAccount | Receiving split payments and internal transfers |
| 60 days | issueCard, useCard and related card capabilities | Issued cards and ATM withdrawals |
| 60 days | receiveFromThirdParty | Receiving funds from third parties |
In total Adyen lists 7 capabilities on the 30-day period and 10 on the 60-day period. A seller with one open error can therefore lose payouts on day 31 while still taking orders until day 61. Sales keep landing in the balance account and nothing reaches the bank. Most sellers who contact us with Adyen payouts disabled after a verification error are in exactly that window.
Standard does not mean guaranteed
Adyen states that, under its internal due diligence processes, a standard deadline can be shortened or removed in specific situations. Treat 30 and 60 as ceilings. Read the actual date in the account holder’s record. Platforms can see it in the Customer Area or through the verificationDeadlines field in Adyen’s API responses and webhooks, and a well-built platform dashboard shows it next to the error.
Deadlines are tracked per capability
One legal entity can carry several open errors, and each capability carries its own deadline. Log every error with its code, the date it appeared and the date attached to each capability it affects. Plan to submit at least 10 days before the earliest date. A rejected document close to the deadline leaves no room for a second attempt.
First-Time Errors, Repeat Errors and the Permanent Outcome
Adyen does not run a strike system for missed verification deadlines. A first-time lapse and a repeat lapse produce the same mechanical result. The capability flips to allowed false and returns once the errors are resolved and the status moves back to valid. The difference shows up in time. Our experience is that a capability already disallowed takes longer to restore than an error fixed inside the window, because the platform has to chase the case with Adyen rather than letting automated checks clear it.
Repeat errors on the same field also tell a reviewer something. A legal name corrected in March and broken again in June looks like a record nobody controls. That invites closer review at the next periodic check.
The permanent outcome is the rejected status. Adyen describes it as final, and its errors cannot be resolved by updating data or uploading documents. A rejected capability is a different problem from a missed deadline, and it usually sits next to an account holder suspension or a business model Adyen does not support, which our article on prohibited platform models explains.
Why Adyen Runs KYC on Platform Users
Adyen is a regulated payment provider. It moves money for account holders it never meets, so anti-money-laundering law in each region requires it to identify them, confirm the business exists and know who owns and controls it. The platform passes along the requests, but the obligation sits with Adyen.
United States
The Bank Secrecy Act rules sit in 31 C.F.R. Chapter X, administered by FinCEN. The Customer Identification Program rule at 31 C.F.R. 1020.220 sets four minimum data points before a bank opens an account. Those are name, date of birth for individuals, address and an identification number, which is a taxpayer identification number for US persons. For an entity, the rule points to documents showing the entity exists, such as certified articles of incorporation or a business license.
Ownership comes from 31 C.F.R. 1010.230. It defines a beneficial owner two ways. One is each individual holding 25 percent or more of the equity, which means up to 4 people. The other is a single individual with significant responsibility to control or manage the entity, such as a CEO or managing member. Covered institutions must keep those records for 5 years. The rule was published on May 11, 2016 at 81 FR 29451. That two-prong structure is why a US seller is asked for both owners and a controlling person, even when nobody owns a quarter of the company.
European Union
Directive (EU) 2015/849, adopted on 20 May 2015, is the current framework. Article 3 treats a shareholding of 25 percent plus one share as an indication of direct ownership. Article 14(5) requires firms to apply due diligence to existing customers at appropriate times, including when their circumstances change. That provision is the legal root of Adyen’s periodic reviews and re-checks after data changes.
Regulation (EU) 2024/1624, adopted on 31 May 2024, replaces most of that framework with directly applicable rules from 10 July 2027. Article 20 sets the customer due diligence measures, Article 26 requires ongoing monitoring of the business relationship, and Article 52 defines an ownership interest as 25 percent or more of the shares or voting rights. EU account holders should expect the same categories of request to continue after 2027, with less room for national variation.
United Kingdom
UK account holders fall under the Money Laundering, Terrorist Financing and Transfer of Funds (Information on the Payer) Regulations 2017, regulation 27. Regulation 27(8) requires due diligence on existing customers at other appropriate times on a risk-based approach, and whenever the firm learns that a customer’s relevant circumstances have changed. A UK director change filed at Companies House but never entered on the platform is exactly the kind of change that can surface during a later review.
How the regions differ in practice
The verification process and the 30 and 60 day table are Adyen’s own and apply wherever the platform operates. What changes by region is the evidence behind each request. A US entity sees questions shaped by the CIP and two-prong ownership rules. An EU or UK entity sees requests shaped by the 25 percent ownership test and the duty to refresh data on existing customers. A document that cleared for a Delaware LLC will not automatically clear for a German GmbH owned by the same founder. Answer the request on screen for the entity registered in that country.
Documents That Clear Adyen Verification Errors
Start from the error code, not from a generic checklist. Adyen’s general error codes name the failed check in plain words, and each one points to a narrow set of documents.
| General error code | Adyen’s message | What usually fixes it |
|---|---|---|
| 1_31 | ID document is needed | Upload a valid government photo ID for the named person |
| 1_33 | ID document didn’t meet requirements | Replace a blurred, cropped or expired ID |
| 1_35 | Individual details didn’t match the ID document | Correct the name or date of birth on the record to match the ID |
| 1_51 | Organization details didn’t match the document | Align legal name and registration number with the registry extract |
| 1_52 | Registration document didn’t meet requirements | Upload a current, complete registry extract |
| 1_53 | Tax document didn’t meet requirements | Upload the tax registration issued in the legal entity’s name |
| 1_55 | Proof of ownership is needed | Upload a shareholder register or equivalent ownership record |
| 1_56 | Organization ownership couldn’t be verified | Reconcile the UBO list with the ownership record |
| 1_70 | Bank account couldn’t be verified | Upload a bank statement or bank letter for the payout account |
| 1_76 | Bank details didn’t match the bank document | Match account holder name and number to the bank document |
Each general error links to sub-errors with a 4-digit suffix, such as 1_5023 under 1_51. Adyen also returns remediating action codes, and its remediating action list spells out the expected move. Code 1_518 reads Update organization legalName. Code 1_703 reads Upload a bank statement. Code 1_102 reads Upload a different document. When a platform shows the account holder only a generic message, ask the platform for the code and the remediating action behind it.
Exact matching decides the outcome
Most rejected submissions are genuine documents that disagree with the record by a word or a digit. “Smith Trading Ltd” on the registry and “Smith Trading” on the account. A payout account in the owner’s personal name when the account holder is a company. A trading name typed where the legal name belongs. Each produces an error such as 1_51 or 1_76 even though nothing is fake.
Compare every field on the document with the record before you upload. When they differ, the record usually changes, because Adyen verifies the record against the document and not the other way round.
Document checklist matched to each item Adyen requests
- Legal entity. A current registry extract or formation document showing legal name, registration number and registered address. Add the change certificate if the name changed.
- Individual identity. An unexpired government photo ID for each named person, spelled exactly as entered, with the date of birth matching the record.
- Beneficial owners. A shareholder register or ownership chart listing everyone at 25 percent or more, plus the controlling person, matching the UBO entries one for one.
- Directors and signatories. A current officer list. Remove anyone who left and add anyone appointed.
- Tax identity. The tax registration in the legal entity’s name, with the number exactly as entered.
- Payout account. A bank statement or bank letter showing the legal entity as account holder and the same account number entered on the platform.
- Address. A document showing the registered or operating address in the form entered.
Upload originals only. An edited, annotated or merged file creates a new error and damages the record.
The payout bank account
Bank errors stop money directly, because sendToTransferInstrument runs on the 30-day clock. The payout account must belong to the legal entity being verified. A company needs a business account in its legal name. A sole trader needs an account in the name entered. Switching banks is itself a data change. Upload the statement for the new account in the same session you enter its details, so the check starts at once instead of waiting for Adyen to ask.
Preparing the files
Capture the full page with all 4 corners visible, no glare and every character readable at 100 percent zoom. Keep multi-page registry extracts whole, because the page listing directors is often the one the reviewer needs. Never crop, highlight or redact unless the request says to.
How Adyen Reviews a Verification Submission
Automated checks run first. They compare each document with the field it supports. Name, number, date and address either match or they do not, and the document is either legible and current or it is not. A field that passes moves toward valid. A field that fails keeps the error open or creates a new one under a different code.
That makes the result predictable. When every field matches, expect the error to clear. When one field is off, expect it to fail no matter how real the business is.
What causes a submission to fail
- A name that differs from the record by a word, an abbreviation or a suffix such as LLC or GmbH.
- An expired ID document.
- A blurred, cropped or glare-covered image.
- An ownership record listing different people from the UBO entries.
- A document issued to a trading name instead of the legal entity.
- A file that has been edited or stitched together.
How a resubmission is read
A reviewer looking at a second attempt wants to see what changed. The same document uploaded again against the same record fails for the same reason. A corrected record plus a matching document clears. Keep a one-line note of the change, such as “legal name on the account corrected to match the registry extract”. When the platform escalates, that line tells Adyen Support where to look.
The platform sits between you and Adyen
Account holders on Adyen for Platforms rarely contact Adyen directly. Uploads go through hosted onboarding or the platform’s own screens, and the platform raises cases with Adyen Support. Adyen notifies platforms of capability changes through the balancePlatform.accountHolder.updated webhook, but its documentation notes that changes to legal entity data alone do not fire that webhook. A platform watching only that signal can miss a change you made. Send the platform your submission confirmation and ask it to check the error list directly.
Step by Step Fix for Adyen Verification Errors
Our working position in these cases is that the identity and the business are genuine. Payouts and held balances should return once matching documents are on file. The steps below aim to get there on the first submission.
- Read the exact error. Open hosted onboarding or the platform dashboard. Write down the general error code, any sub-error, the remediating action and the deadline date for each capability.
- Name the root cause in one line. In our files it is nearly always one of four things. A periodic refresh found an outdated document, a name or registration number does not match, a document was unreadable, or an ownership change was never entered.
- Correct the record first. Update owners, directors, legal name or payout account so the record matches the legal documents. A correct document against a wrong record still fails.
- Gather matching originals. Collect identity, formation, ownership and tax documents in the exact legal name. Reconcile the same name, number and address across the platform, the bank and the tax authority.
- Run the quality check below. Catch mismatches before Adyen does.
- Submit through the platform. Upload in hosted onboarding or the platform’s screens and save the confirmation with its date and time.
- Escalate if it does not clear. If the error is still open after the review, send the platform the confirmation and your one-line change note, and ask it to raise the case with Adyen Support.
- Confirm the result. Check that the error is gone, that each capability shows allowed, and that the next payout lands. Record the date it cleared.
Submission quality check for name matches, dates, legibility and ownership
- Name. The legal name on every document is identical to the record, suffix included.
- Numbers. Registration and tax numbers match digit for digit.
- Address. The document address is the one entered, in the same form.
- Dates. IDs are unexpired. Statements and letters are recent enough for the request.
- Legibility. Every character readable, all corners visible, no glare.
- Completeness. Every page present, nothing cropped.
- Ownership. The UBO entries equal the people on the ownership record, nobody missing and nobody extra.
- Unaltered. No edits, highlights or annotations.
A worked example
Take a hypothetical furniture maker selling through a marketplace built on Adyen. One of its 2 founders sells his shares and leaves. Nobody updates the platform. At the next periodic review Adyen flags 1_56, organization ownership couldn’t be verified, and sets deadlines. The seller ignores the banner during peak season. On day 31 sendToTransferInstrument is disallowed and payouts stop, while receivePayments keeps working until day 60. Orders keep coming in and the balance keeps growing with nowhere to go.
The fix takes three moves. Remove the departed founder from the UBO entries. Upload the updated shareholder register showing the remaining owner at 100 percent. Upload the share transfer record that dates the change. Every name and date now matches. The marketplace escalates with the confirmation and payouts resume after review. Done before day 30, the same three moves would have caused no interruption at all.
When payouts have already stopped
The method stays the same, with two additions. Ask the platform to confirm the balance that built up while payouts were off and record the figure. Ask for an expected timeline once the package is in, and follow up the day it passes. When the platform is slow to escalate, our Adyen disputes service builds the package and the escalation file together.
Mistakes that make it worse
- Opening a second account holder profile to keep receiving funds.
- Re-uploading the rejected document without fixing the mismatch.
- Uploading edited or merged documents.
- Waiting for the payout to fail before reading the error.
- Moving funds in ways that conflict with the Adyen for Platforms verification process.
Periodic Data Reviews and the 3_10 Error
A periodic review shows up as verification error 3_10, Review of data is required, with remediating action 3_100. Adyen’s data review documentation says the account holder must confirm the data, and if checks find errors, resolve those as well. Confirming alone does not finish a review that has open errors. The capabilities stay allowed until the deadline in the review notice passes.
Platforms can ask Adyen for a review early, which helps with sellers who log in rarely. Adyen refuses that request in three cases. The account holder was onboarded within the past 180 days, the last review happened within the past 180 days, or the next scheduled review is more than one year away. Adyen may also demand a review outside the normal schedule after a significant change in the account holder’s information or risk level. Our full walkthrough of the Adyen periodic data review covers the confirmation flow screen by screen.
Prevention Routine That Keeps Capabilities Allowed
Resolve each error the day it appears and track the earliest 30-day date for every account holder. Data changes and periodic reviews bring verification back for the life of the account.
By business model
Marketplace sellers. Treat every verification banner as a payout deadline. Read it the day it arrives and log the date. The sellers who lose payouts almost always saw the prompt and put it off.
Businesses with changing owners or directors. Enter the change on the platform the week it happens, with matching documents ready. A director appointed, a shareholder bought out and a founder leaving are each a data change Adyen re-verifies. Our article on registration changes Adyen was never told about covers what happens when that update is skipped.
Companies with trading names. Put the legal entity name on the account and keep the trading name for the storefront. Every document must carry the legal name.
Sellers in restricted categories. A category approval adds its own checks on top of standard KYC. See Adyen restricted category approval before adding regulated products.
For platform operators
Open errors among your sellers are your support load and your churn risk. Show each error to the seller the day it appears, display the deadline per capability, and send reminders at 14 days and 7 days before the earliest date. Keep an internal list of every open error sorted by deadline so your team chases the closest ones first. Do not rely on the account holder webhook alone, because legal entity data changes do not fire it. Escalate to Adyen Support with the seller’s confirmation and change note together. Complete escalations come back faster than forwarded complaints. A platform that ignores this tends to meet Adyen again over card scheme fines passed through or other account-level issues.
The weekly routine
- Keep one legal identity across the platform, the bank and the tax records.
- Store current copies of ID, formation, ownership and tax documents ready for a refresh.
- Check the dashboard for verification errors once a week.
- Log each error with its code, the date it appeared and each capability deadline.
- Diary ID expiry dates for every named person and renew 60 days ahead.
- Enter ownership, director, address and bank changes the week they happen.
- Confirm with the platform when each error clears and record the date.
Frequently Asked Questions
What triggers an Adyen verification deadline?
A failed check after a data change, a periodic data review or a contractual step such as new Terms of Service triggers it. Adyen sets the deadline only when verification errors are open and the platform uses Legal Entity Management API version 3 or 4.
How many days do I have to fix Adyen verification errors?
The standard period is 30 days for capabilities that send funds out, including payouts, and 60 days for capabilities such as receiving payments and issuing cards. Adyen can shorten or remove a standard deadline, so read the date shown for each capability.
Why are my Adyen payouts disabled after verification when I can still take payments?
Payouts run on sendToTransferInstrument, which has a 30-day deadline, while receivePayments has 60 days. A single unresolved error stops payouts first and payments about a month later.
Can Adyen capabilities disallowed after a deadline be restored?
Yes, when the status is invalid. Fix the errors, submit matching documents and the capability returns once verification passes. A rejected status is final and cannot be fixed by uploading documents.
What does Adyen error 3_10 mean?
It means Adyen requires a review of the account holder’s data. The matching remediating action is 3_100, and the review is complete only when the data is confirmed and every error is resolved.
Which Adyen for Platforms KYC documents do I need?
The error code decides it. Most cases need a registry extract, government photo ID for each named person, an ownership record covering everyone at 25 percent or more and a bank statement in the legal entity’s name.
How long does an Adyen document review usually take after upload?
Adyen does not publish a fixed review time for account holder documents. Save the submission confirmation with its date, and if the error is still open after the platform’s stated timeline, ask the platform to escalate with that confirmation.
Get Help With an Adyen Verification Deadline
Most Adyen verification errors clear on the first upload when every field matches the record. We step in when payouts have already stopped and the platform is slow to take the case to Adyen. We read the exact codes, reconcile the entity record against the registry, bank and tax documents and hand the platform a package it can escalate the same day.
Start with our Adyen disputes and funds release service, or book a consultation for a free assessment of your open errors. Sellers dealing with more than one processor can compare the rest of our banking and fintech recovery work.
Sources
- Adyen Docs, Adyen for Platforms verification overview and verification deadlines
- Adyen Docs, user capabilities and verification statuses
- Adyen Docs, periodic data reviews
- Adyen Docs, general verification error codes
- Adyen Docs, remediating action codes
- eCFR, 31 C.F.R. Chapter X, FinCEN regulations
- eCFR, 31 C.F.R. 1020.220, Customer Identification Program
- eCFR, 31 C.F.R. 1010.230, beneficial ownership requirements
- EUR-Lex, Directive (EU) 2015/849
- EUR-Lex, Regulation (EU) 2024/1624
- legislation.gov.uk, Money Laundering Regulations 2017, regulation 27