Paynetics' White Label Digital Wallet comes in two distinct types. The choice between them is not a feature preference — it's driven by how you acquire users and how cards reach them. This article gives you a side-by-side view of what each type supports and a decision aid to pick the right one.
For the high-level product description see the Digital Wallet Overview. For the complete feature reference, including KYC document requirements, see Digital Wallet Features.
Quick Comparison
Feature | Issuing Wallet (Open) | Invite-Only Wallet (Linking) |
|---|---|---|
Who can register | Any user who downloads the app | Only users pre-created by the partner |
How users get access | Self-register with phone number | Invited by partner; link a pre-assigned card |
Card provisioning | User self-issues virtual / physical cards | Partner pre-creates the card; user links it |
Cards per user | 1 virtual + 1 physical (per type) | 1 card per account |
KYC options | KYC Full only | Partner Managed, KYC Standard, or KYC Full |
P2P transfers | ✓ | ✗ |
Outbound wire transfers | ✓ | ✗ |
User-initiated top-up by card | ✓ | ✗ |
P2P QR / payment link | ✓ | ✗ |
Partner-initiated top-up | ✓ | ✓ |
Inbound wire transfers (IBAN) | ✓ | Configurable (not available for commercial-card accounts) |
Apple Pay / Google Pay | ✓ (if certified) | ✓ (if certified) |
Loyalty card digitisation | ✓ | ✓ |
Pricing plans | Up to 2 plans | 1 plan only |
Promotional engine | ✓ (paid-for-free mechanic) | ✓ (limited) |
Commercial cards | ✗ | ✓ |
Decision Aid
Pick the Issuing Wallet if… | Pick the Invite-Only Wallet if… |
|---|---|
You want a publicly available consumer fintech app | You control exactly who participates (employees, members, closed-loop community) |
Your users self-onboard and manage their own payment experience | You pre-issue cards and want users to link them, not order new ones from the app |
You need the full wallet functionality — transfers, P2P, top-up by card, QR payments | Your customers already have cards from your own programme, typically under BIN Sponsorship, and you need an engagement layer rather than a full bank |
You're comfortable with KYC Full as the only verification path | You need Partner-Managed KYC because you already verify your customers, or KYC Standard for business-card programmes |
You want users to self-issue virtual and physical cards | You want to deploy commercial (business) cards to user accounts |
Issuing Wallet (Open for Registration)
The Issuing Wallet is designed for consumer-facing applications where any user can download and register freely.
User Journey
User downloads the branded app.
User registers using their mobile phone number.
User sets a PIN and confirms their identity via OTP.
User can explore the app but cannot use payment features until KYC is completed.
After successful KYC Full verification, the user gains access to all payment features.
User can self-issue a virtual card (and later a physical card) from the Cards tab.
Key Characteristics
IBAN assignment: every verified user receives their own unique IBAN for inbound SEPA / BISERA transfers.
Unique registration: a user can only have one account per wallet, even if they have multiple phone numbers.
No commercial cards: the Issuing Wallet does not currently support issuing Commercial cards or Business accounts.
Fee plans: up to two pricing plans, each with the full set of configurable fee parameters — see Digital Wallet Features for the fee tables.
Invite-Only Wallet (Linking Wallet)
The Invite-Only Wallet is designed for controlled programmes where the partner decides exactly who participates and pre-provisions accounts and cards for them.
This wallet is the natural companion to BIN Sponsorship: if you run your own card programme on a Paynetics-sponsored BIN, the Invite-Only Wallet is the engagement layer your customers use to manage those cards — secure login, card controls, transaction history, push provisioning to Apple Pay and Google Pay. You keep ownership of the cardholder ledger and the cards themselves; the wallet is the consumer-facing surface.
User Journey
Partner creates a user record and assigns a card via API or batch CSV upload.
Partner sends the user an invite (email or custom channel) containing an Authorization code and Card code.
User downloads the app, registers with their phone number and enters the codes to link their card.
User can begin spending immediately after linking (subject to any applicable KYC).
If the user wishes to link a different card, Customer Support must be involved — consecutive card-linking is not self-service.
Key Characteristics
One card per account: the Invite-Only Wallet supports only one linked card per user account.
IBAN: optional per configuration; not available for users holding a commercial card (the linked account is owned by the card's business).
Commercial cards supported: partners can link business / commercial cards to invite-only user accounts.
KYC flexibility: Partner-Managed KYC, KYC Standard or KYC Full can be configured depending on the programme's requirements.
KYC by Wallet Type — Summary
KYC Type | Issuing Wallet | Invite-Only Wallet | Description |
|---|---|---|---|
KYC Full | ✓ | ✓ | Full document + liveness video check in-app; Paynetics verifies |
KYC Standard | ✗ | ✓ (business cards only) | Name, nationality, DOB collected during card linking; no document upload |
Partner Managed | ✗ | ✓ | Partner submits pre-verified customer data; Paynetics approves and audits |
For document requirements by country, the KYC status model, common failure reasons, occupation declarations and the PEP declaration for Bulgaria, see Digital Wallet Features.
Switching Wallet Types
The wallet type is set at configuration time during onboarding. It is not possible to switch between Issuing and Invite-Only after go-live. If your use case has elements of both types, raise it with your Paynetics account manager during pre-boarding and we can scope the closest fit.