Payment processors readiness

This guide is for businesses that need to accept card or online payments (e.g. Stripe, PayPal, Adyen) and want to understand processor requirements, risk categories, and evidence of delivery. It is not for you if you only need a bank account and no card/online processing.

Payment processors assess risk separately from banks. A bank account does not guarantee processor approval. Processors care about business model, delivery evidence, chargeback risk, and compliance with their acceptable-use policies. Having a clear narrative and proof of delivery helps; high chargeback rates or restricted categories hurt.

Setup can be quick (days) once documents are ready; underwriting for higher-risk or complex businesses can take longer. See Costs, timelines, hidden fees for context on overall project timelines.

Typical processor requirements: ID and address verification; company registration and UBO details; website and business description; sometimes bank statements or proof of delivery (invoices, tracking, service agreements). Restricted or high-risk categories may need additional policies (e.g. refund, chargeback) and evidence. Check each provider’s list; see also Bank account opening checklist and Bankability checklist.

Common failures: applying without delivery evidence; operating in a restricted category without disclosure or policies; high chargeback ratio; inconsistent business name or website; missing or vague business description. See Red flags & scams for buyer due diligence when choosing providers.

If one processor declines, others may accept your profile; compare provider lists and risk categories. For some use cases, invoicing and bank transfers suffice; see Agency/consulting. For e-commerce, see E-commerce.

What is evidence of delivery?

Proof that you deliver what you sell: e.g. tracking for physical goods, signed contracts or completion certificates for services, login or access for digital products. Processors use it to reduce fraud and chargeback risk.

Which categories are restricted?

Lists vary by processor. Common restrictions include certain adult content, gambling, crypto, CBD, high-risk health claims, and others. Check each processor’s acceptable-use or prohibited list before applying.

Do I need a bank account first?

Usually yes. Processors typically pay out to a verified bank account in the entity’s name. Some offer accounts themselves; requirements still apply.

What if I sell digital services?

Processors often want evidence of delivery: e.g. login/access, contracts, or invoices showing service completion. Have a clear process and terms; see SaaS use case.

Why was my application held or declined?

Processors rarely give detailed reasons. Common causes: missing delivery evidence, restricted category, high chargeback risk, or inconsistent information. Strengthen documentation and try another provider if appropriate.

• Start here — decision flow.
• Jurisdictions — where to set up.
• Bank account opening checklist — KYC and narrative.
• SaaS selling globally — payments and proof.
• Bankability checklist — printable readiness.
• Request introductions — when you are ready.