Verification volume, branch count, and integration depth vary a lot between a single pilot branch and a nationwide rollout — so every plan is quoted, not shelf-priced.
Pilot
One branch, prove it works
Custom quote
Growth
Multiple branches, one institution
Custom quote
Enterprise
Full platform, dedicated support
Custom quote
| Feature | Pilot | Growth | Enterprise |
|---|---|---|---|
| Branches / desks | 1 branch, 3 desks | Unlimited | Unlimited |
| Consumer app + Merchant Desk | |||
| Institution Console | |||
| Branch-scoped analytics | |||
| Priority support | |||
| Custom SLA | |||
| Dedicated integration support | |||
| Named account manager |
Cost depends on branch count and verification volume, both of which vary a lot between a single pilot branch and a nationwide rollout. A quote sized to your actual scale is more honest than a one-size number.
It depends on integration depth — a straightforward Merchant Desk pilot looks different from a full Institution Console rollout with custom KYB requirements. This is part of what gets scoped in a quote.
Verification usage and billing are managed per institution through the Institution Console's own Billing tab — invoices and payment status are visible there directly.
Yes — Pilot is designed to prove the model at one branch before a network-wide rollout, and moving to Growth or Enterprise doesn't require re-integrating anything.
Request a quote
Tell us about your institution and we'll size a plan to it.