Authorised volume
Spend that used to leave as a transfer arrives as card volume on your own BIN.
For issuers & banks
Capture the volume that is walking out of the door
Make every card you have issued a wallet card.
Every withdrawal is authorised volume you never saw. Accept² lets that balance pay on a card you already issue.
The commercial case
Three lines that move
Interchange on new flow
Card economics apply to every funded transaction — on volume you earn nothing from today.
Primacy and engagement
A card that can spend from any balance the customer holds is the card that comes out of the wallet first. Top-of-wallet is won by usefulness, not by campaigns.
Risk posture
What changes, and what pointedly doesn't
The review that kills most partnerships asks who holds the credential, the decision and the liability. All three answers stay yours.
Accept² returns a funding answer. The issuer approves or declines.
The design constraint the whole platform is built aroundUnchanged
- Your BIN, your licence, your scheme membership
- Your authorisation decision and your risk models
- Your cardholder relationship and your brand on the card
- Your settlement cycle and your acquirer relationships
- Your dispute and chargeback handling
Getting there
From first conversation to first tap
Nobody turns this on portfolio-wide at once. Start with a scoped pilot, measured against your own withdrawal data.
Size the leak
Using your own data: how much balance leaves the ecosystem as transfers and withdrawals each month, from which segments, at what cost to you in lost volume.
output segment-level withdrawal baseline
time 2–3 weeks
time 2–3 weeks
Design the policy
Which balances are eligible, in what order, under what limits and merchant categories, and exactly what happens on a shortfall. Written as policy, tested against replayed traffic.
output versioned funding policy
time 3–4 weeks
time 3–4 weeks
Integrate and certify
Connect the authorisation path and the funding sources, run the scheme and security review, and prove latency against your own host under load.
output certified integration
time 6–10 weeks
time 6–10 weeks
Pilot, then widen
A limited cardholder cohort goes live. Funded volume, withdrawal displacement, decline reasons and support load are measured against the baseline before anything scales.
measure funded volume vs withdrawal baseline
then widen by segment
then widen by segment
Indicative durations for a mid-size issuer. Real timelines depend on your authorisation architecture, change calendar and internal review cycles.
The alternatives
Three ways to unlock a balance
| Withdraw to bank | Build a card programme | Accept² | |
|---|---|---|---|
| Time to first payment | 1–3 days, every time | 12–18 months | Weeks |
| Balance stays with you | No — this is the leak | Yes | Yes |
| Licensing needed | None | BIN sponsor, certification, licence | Your existing licence |
| New card to adopt | n/a | Yes | None |
| Balances per payment | One, manually | One funding account | Several, split by policy |
| Merchant integration | None | None | None |
Objections worth raising early
The hard questions
It shouldn't, and the pilot proves it either way. The target is balance leaving as a withdrawal — volume that never reaches your rails. Measured against a pre-agreed baseline, by segment.
A single synchronous call with a strict budget, well inside the scheme timeout, proven against your own host under load. If Accept² can't answer in time, your normal default applies.
Exactly where it sits today. Your BIN, your dispute rules, unchanged. Accept² adds the evidence trail — which source funded it, under which policy version.
Put it early. Accept² is a technology provider doing decisioning on your behalf. It does not issue credentials, hold funds or provide regulated services.
Start with your own withdrawal data.
The first conversation is usually about sizing the leak. Bring the numbers you already have and we will show you what they would look like as card volume.