Merchant onboarding

One merchant profile. Multiple PSP choices.

Prepare one comprehensive application, then map the right information to each selected payment provider. Final requirements remain country, entity, product and risk dependent.

Planning workspace

No application, identity document or bank detail is sent to a PSP from this preview.

Do not upload sensitive documents until secure storage and provider connections are activated.

Step 01 · Choose providers

Build the right checklist.

Select one or more PSPs. Negotiating and coming-soon providers can be included for planning, but cannot be submitted until the relevant commercial and technical connections are live.

Build checklist

The selected registration country determines the legal document route. Review country-specific legal documents.

Step 02 · Preparation checklist

Prepare once. Route intelligently.

This is a preparation checklist, not a guarantee of approval. The selected PSP remains responsible for its final verification, underwriting and additional information requests.

Business profile

Identify the legal entity, its activity and where it operates.

People and ownership

Prepare the people records needed for KYC and signing authority.

Settlement and finance

Match the legal entity to the account that will receive payouts.

Processing and risk profile

Give underwriting teams a complete view of the payment model.

Website and policies

Make the customer journey and business model verifiable online.

Documents and consent

Prepare evidence without sending sensitive files to Averis yet.

Provider-specific steps

Complete these only when the relevant PSP is selected.

Future integration layer

API-ready by design.

The public contracts are reserved now. Provider credentials, document storage, authentication and webhook verification remain disabled until the production security review is complete.

GET
/api/onboarding/providers

Provider availability and capability manifest

POST
/api/onboarding/requirements

Country, entity and PSP requirement resolver

POST
/api/onboarding/applications

Create an idempotent merchant application

POST
/api/onboarding/webhooks/:provider

Receive signed provider status events

Official requirement sources

Stripe Connect verificationPayPal seller onboardingAzupay Clients APINorth Merchant Boarding APIAdyen verification requirementsCheckout.com business verification

Requirement map reviewed 9 September 2026. Provider rules can change; production onboarding must retrieve current requirements from each PSP.