Merchant onboarding guide · 9 min read
Merchant account application documents: what to prepare before submission
A merchant account application moves faster when the business, ownership, processing and website evidence are complete before an acquirer reviews the file. This guide groups the documents that payment teams commonly collect and explains what each group is meant to prove.
1. Company and registration documents
Start with the legal entity: certificate of incorporation or registration, current company-register extract, constitutional documents where applicable, registered address, tax or VAT information and the trading names and domains used by the business.
The legal name, website terms, bank account and application should agree. Differences between the brand and the entity are normal, but the relationship should be clear.
2. Directors, shareholders and beneficial owners
Collect the ownership and management structure together with valid identity documents and recent proof of address for the people the acquirer must verify. The exact ownership threshold and document standard depend on the acquiring institution and jurisdiction.
If ownership passes through other companies, prepare the chain to the ultimate beneficial owners rather than sending disconnected company documents.
3. Bank and processing evidence
A bank statement or bank confirmation establishes the settlement account. Existing merchants are commonly asked for processing statements showing volumes, refunds and chargebacks; a new merchant may instead need forecasts or a business plan.
Prepare projected monthly volume, average ticket, maximum ticket, currencies, target countries, delivery time and whether sales are one-off or recurring. These facts influence both risk review and acquirer fit.
4. Business licences and regulated activity
If the merchant operates in a licensed activity, include the relevant licence or registration and make sure the licensed entity, domains and target markets line up with the application. Gambling, financial services and other regulated verticals usually require additional evidence.
5. Website and customer-policy evidence
Before submission, check that the website clearly shows the legal business identity, pricing, terms and conditions, privacy information, refund or cancellation policy, delivery information and subscription terms where recurring billing is used.
An acquirer may also need test credentials for a gated customer journey and proof that the applicant controls the domains being submitted.
6. PCI and payment-security information
The required PCI DSS evidence depends on how card data is handled and on the merchant’s integration. The merchant or payment team should determine the correct validation route rather than assuming the same questionnaire applies to every setup.
7. Review the file before sending it
A complete document folder is not automatically an approvable merchant. Review the identity behind the business, the website, risk signals, chargeback history and the consistency of the answers before selecting an acquirer.
Merchant Scanner keeps the application and uploads in one private onboarding flow, shows what is still missing and carries the completed file into identity review, underwriting and acquirer matching.
Questions
Frequently asked questions
What documents are usually required for a merchant account application?
Common requirements include company registration documents, ownership and director evidence, KYC documents, bank evidence, processing history or forecasts, licences where relevant, website policies and the applicable PCI DSS information. Exact requirements vary by acquirer and merchant risk profile.
Do new merchants need processing statements?
A new merchant may not have processing history. In that case an acquirer can ask for forecasts, a business plan and other evidence supporting expected volume and business activity.
Why do merchant account applications get delayed?
Common causes are missing or expired KYC documents, inconsistent entity details, incomplete processing information, unclear ownership, missing website policies or additional questions raised during risk review.