From a company name
to a signed contract.
Six steps that collect everything the contract needs — and never ask for it twice.
Configured to your requirements
Every acquirer collects something different. Steps, fields, documents and validation rules are configured per partner — the merchant is only asked for what you need.
Onboarding data lands in your systems
We push completed applications into the acquirer's or provider's own systems over API — merchant records arrive where your teams already work, not as an export someone re-keys. Each connection is scoped with the partner.
A link the merchant can finish alone
Send a public self-service link and the merchant completes the application without anyone from your team in the portal — or run the same flow as a guided in-portal wizard. Same data, same contract, either way.
Live registry lookup
The merchant types a company name; we pull the rest from the national business registry. Companies and sole traders alike.
Your team can take it over
If a merchant stalls halfway through, your team picks the application up remotely and completes it.
Onboard once, provision many
One sign-up provisions every product the merchant ordered — terminal, POS, fiscalisation, services. Nothing is asked twice.
The contract isn't only about cards
The contract is generated from a template, signed electronically and filed — with resend, reversal and a full audit trail, and a signing pipeline each ISO can switch on or off. Prices come from the product catalogue, so change a price once and every new contract picks it up.
Card acceptance is only one part of it. Because the data is already on file, adding a product later is an activation, not a second onboarding.
Adding a product later is an activation — not a second onboarding.
Because the data is already on file.
