Skip to content

From application to live, with officers on the exceptions

Digital merchant onboarding from application to live acceptance. Document AI reads the files and screening runs first, so officers review the exceptions instead of every file.

An officer reviewing documents at a desk with a laptop

Applications as a flow

Every application moves from applied through documents, review and activation to live, with a count at each stage and the waiting time against the institution's policy on every row.

  • A screening match named as a match to clear, not hidden in a status
  • Applications waiting on the institution listed on the dashboard, oldest first

Applied AI reads the documents first

The platform's document AI reads each application's documents and screening runs before a person looks, so officers review the exceptions instead of every file.

Documents on the record, with expiry

SSM registration, TIN, the directors' identity and proof of the settlement account are held on the merchant record, each with an expiry date, and a penny test on the settlement account is recorded before activation. An examiner is answered from the screen.

  • The record turns amber before a document expires
  • The merchant sees the same documents and uploads renewals

Screening, limits and holds

Screening runs at onboarding and every month. Limits are set by risk tier and can be changed per merchant, and the institution's own rules hold, decline or alert. A hold is a case with a reason, the numbers behind the rule and an owner.

  • Sanctions and PEP, SSM status and adverse media
  • Per-transaction and daily limits, with a rolling reserve where the tier needs it
  • Fraud rate against the scheme threshold, beside declines by risk

See it with your own merchants

Send us the methods you take, the number of merchants and the payment and account systems in place. An engineer replies with a rollout plan, a list of decisions to agree and a proposal.