Registration that
configures the account.
The full registration flow for new merchants - dynamic application forms, KYC and KYB orchestration, document handling, scoring and provisioning.
Registration as a configurable workflow
Every PSP runs registration differently - different verticals need different forms, different KYC providers, different scoring criteria. Merchant Registration is built around the assumption that the registration workflow is part of the configuration.
Dynamic forms
Registration is not a formality that produces a record. What the merchant submits drives the verification that runs, the checks that are applied and the configuration the account ends up with.
KYB orchestration
Each application routes through the right KYC and KYB providers - Sumsub, GetID, ShuftiPro, Trulioo or others - based on the merchant type.
Auto-provisioning
Merchants upload required documents through the registration portal. The platform routes documents to KYC providers automatically; merchants are notified of issues.
Rules-driven scoring
The rules engine scores each application against your criteria; auto-approves, queues for review or rejects.
White-label registration
The registration portal is fully white-labelled - your domain, your visual identity. The merchant never sees Coriunder.
How registration runs
- Form
Merchant fills out the application form for its merchant type. Required fields and documents specified by the form configuration.
- Verify
KYC and KYB providers verify identity and incorporation; documents reviewed; rules engine scores the application.
- Provision
On approval, MIDs provisioned, fee templates applied, login credentials issued. Live for transactions.
Frequently asked questions
How long does registration take?
For a straightforward application the path from submission to a usable account is short, because verification and provisioning run from the submission rather than waiting for someone to start them. Applications that need a human decision take as long as that decision takes.
Can I have different forms per merchant type?
Yes. Build as many forms as you need. The rules engine assigns the right form based on the merchant's self-classification or other application data.
Which KYC providers are integrated?
Verification is routed per programme, so different merchant types can go to different providers automatically rather than everything landing with one. Which providers are enabled depends on your deployment.
Can I white-label the registration portal?
Yes. Fully white-labelled - your domain, your visual identity. The merchant never sees Coriunder.
How are document re-uploads handled?
When a document fails verification, the merchant is notified through the portal with the specific issue. Re-upload from the portal triggers automatic re-verification.
Where is data hosted?
Hosting, retention and data residency are set per deployment rather than fixed, and each brand is served from its own domain. Tell our team what your regulator and your customers require and we will confirm the arrangement in writing.