Issue Payment CardThe platform this wallet's virtual cards are issued from.
Digital Wallet
A modern, mobile-first payment experience, without replacing the card program you've built.
Explore Other Solutions
On This Page
Reading time: ~4 Min ReadDigital wallet issuance runs on two distinct rails: an in-app wallet for closed-loop cards, tokens, and vouchers with no scheme dependency, and Apple Pay / Google Wallet provisioning for open-loop cards, live in production today.
Virtual cards issue instantly, a new customer can start paying before a physical card arrives, and a lost card is replaced in seconds, not days.
Prepaid and credit account structures, plus a full voucher engine, run on the same platform as your physical card program, not a separate system to reconcile.
What's The Difference Between An In-App Wallet And Apple Pay / Google Pay Support?
They're two different things, and most programs need both. Inside your app, the cardholder carries their closed-loop cards, tokens, and vouchers, and pays directly from the app itself, no plastic, no scheme dependency. Apple Pay and Google Wallet provisioning puts open-loop card credentials on the device instead, for NFC and in-app payment outside your own app.
Instant Virtual Cards
New customers can start paying before a physical card arrives, and a lost or stolen card is replaced in seconds - no reissue delay.
Two Kinds Of Wallet, One Platform
Run in-app and Apple Pay / Google Wallet side by side from a single platform. Open-loop provisioning is live in production today, with Reins bringing the token-service-provider partner if you don't already have one.
Unified Management
Virtual and physical cards run on the same platform with unified controls, spending rules, and reporting, not a parallel system to reconcile.
Prepaid & Credit, Built In
Limits, exposure monitoring, credit-stop, and top-ups for both prepaid and credit account structures, live across production programs.
Vouchers & Promotions, Not Just Cards
Issue vouchers to phone or email, as a targeted campaign or a one-off service recovery, with expiry, single-use enforcement, and full redemption reporting.
No Physical Card Required
Reduce issuance costs and accelerate onboarding: a customer can start transacting on a virtual card alone, or stick to physical cards only if they prefer. It's just a click on the platform.
Compliance Handled At The Infrastructure Level
Wallet provider reporting requirements, scheme updates, and new wallet specifications are managed centrally, not chased page by page.
How You Do It
How Does A Card Actually Get Into A Customer's Digital Wallet?
A new card is issued instantly, usable before any physical card arrives.
Closed-loop cards, tokens, and vouchers go into the in-app wallet, no scheme dependency. Open-loop cards go through the device wallet (Apple Pay / Google Wallet), provisioned via a token service provider.
Open-loop cards only: credentials are provisioned into Apple Pay or Google Wallet, enabling NFC and in-app payment. In-app wallet cards skip this step, they're ready to use inside your app as soon as they're issued.
Virtual and physical cards share the same controls, spending rules, and reporting, no parallel system to reconcile.
Physical-Card-Only vs. Bolted-On Mobile Wallet vs. Reins
How Do They Actually Compare?
| Capability | Physical-Card-Only Program | Bolted-On Mobile Wallet | Wallet-Native |
|---|---|---|---|
| Time to first transaction | Days, waiting on a physical card | Days, waiting on a physical card | Instant — virtual card issues immediately |
| Lost card replacement | Days for reissue | Days for reissue | Seconds, replaced in the app |
| Wallet types supported | None | A device wallet alone still leaves closed-loop cards, tokens, and vouchers with nowhere digital to live — most programs end up running two systems instead of one. | In-app wallet and device wallet (Apple Pay / Google Wallet) |
| Funding model | Whatever the base program supports | Vendor-dependent | Prepaid and credit, both live |
| Compliance overhead | Not offered | Chased per scheme update | Handled at the infrastructure level |
| Reinvent Growth | Not offered | Rarely | Always - the same platform adds wallet, loyalty, and marketing layers as you grow See Solutions |
Physical-Card-Only Program
Bolted-On Mobile Wallet
Reins — Wallet-Native
FAQ.
The in-app wallet holds closed-loop cards, tokens, and vouchers directly inside your app, with no scheme dependency. Apple Pay and Google Wallet provisioning is for open-loop cards specifically, it puts card credentials on the device itself for NFC and in-app payment, and requires a BIN and a token service provider.
Instantly. A virtual card is issued before any physical card arrives, so a new customer can start transacting the same day.
It's replaced in seconds from the app, not days from a reissue queue; the customer gets a new virtual card immediately while any physical replacement is in transit.
Both. Prepaid and credit account structures, including limits, exposure monitoring, credit-stop, and top-ups, are core platform capabilities, live across production programs.
Yes. Vouchers can be issued to phone or email, as a targeted campaign or a one-off, with expiry, single-use enforcement, and full redemption reporting.
No. Reins can bring the necessary token-service-provider partner if you don't already have one; device-wallet provisioning is live in production today.
No. Virtual and physical cards run on the same platform, with unified controls, spending rules, and reporting.
Related Solutions.
Open Loop Card SupportDevice-wallet provisioning (Apple Pay / Google Wallet) is specific to open-loop cards; this is where that acceptance model lives.







