Card Issuing Under Your Own Brand
Your name on the card, your app, your pricing. The issuing relationship, the compliance framework and the ledger underneath are ours.
Speak to Sales See the Fees
What White Label Actually Means Here
Building a card programme from nothing means finding an issuer, passing their security and compliance review, building a ledger that reconciles to the cent, integrating verification, and staffing compliance before the first card ships. Eighteen months is a normal timeline, and most of it is not engineering.
White label means you inherit ours. Your customers see your brand from the first screen to the plastic; the issuing relationship, the compliance programme, the ledger and the reconciliation are ours to run and ours to answer for.
This is not a referral arrangement dressed up: your customers are yours, you set your own pricing, you keep the relationship. What you cannot change is the compliance rules — they come from the issuer and from the law.
What You Get
Everything below is included rather than priced as a module.
Your brand end to end
Card artwork, the app or web interface, the emails, the domain. Nothing your customer sees carries our name unless you want it to.
Virtual and physical issuing
Cards issued through our issuing partner under your programme, provisioned into Apple Pay and Google Pay, shipped where physical cards are required.
APIs for everything the interface does
Create a user, run verification, issue a card, set a limit, freeze, query the ledger, stream transactions by webhook. If the dashboard can do it, the API can.
The compliance framework
Identity verification, sanctions and politically-exposed-person screening, transaction monitoring, and the reporting obligations that come with them, run as part of the programme.
The ledger and reconciliation
Double-entry, reconciled daily against the issuer. The single hardest part of a card programme to build correctly, and the one nobody sees until it is wrong.
Second-line support
Your team answers your customers. When a question is about the rail rather than your product, it escalates to us with an answer rather than a shrug.
Who Does What
The division below is not a preference; it follows from who holds the regulatory permissions.
| You | NELVOI | |
|---|---|---|
| Brand, interface and customer relationship | ✓ | — |
| Pricing to your customers | ✓ | — |
| Customer acquisition and first-line support | ✓ | — |
| Issuing relationship and card scheme membership | — | ✓ |
| Identity verification and ongoing screening | — | ✓ |
| Transaction monitoring and regulatory reporting | — | ✓ |
| Ledger, settlement and reconciliation | — | ✓ |
| Decisions to decline or freeze on compliance grounds | — | ✓ |
The last row is the one worth reading twice. Compliance decisions cannot be delegated to a partner, and any provider offering you control over them is describing something that will not survive its first regulatory review.
From Conversation to First Card
Realistic rather than optimistic. A programme that launches in six weeks is a programme where somebody skipped something.
Scoping
What you are building, for whom, in which markets, and at what expected volume. We tell you at this stage which parts of it we cannot support, because that answer does not improve later.
Commercial terms
Setup, per-card and volume economics, written down. We do not quote a range on a public page because the answer genuinely depends on volume and market mix, and a range wide enough to be honest would be useless.
Programme approval
Your programme is reviewed by the issuing partner: business model, target market, compliance arrangements, financial standing. This is the stage that takes the longest and the one nobody can shortcut.
Integration
Sandbox credentials on day one of this stage. Most teams integrate the core flows in two to four weeks; the long pole is usually your own onboarding UX rather than our API.
Launch
A limited cohort first, then wider. Programmes that open to everyone on day one discover their edge cases with real customers' money.
How the Money Works
Three components, and we would rather set the shape of it out here than have you discover it in a proposal.
- A setup fee — one-time, covering programme approval, configuration and integration support
- A per-card fee — charged once per card issued, virtual and physical priced differently
- A share of transaction economics — the part that scales, and the part where volume genuinely changes the number
Questions About White Label
Yes. What you charge your customers for issuance, subscriptions or conversion is yours to decide, and it is one of the main reasons to run a programme rather than resell one. What you cannot do is charge in a way that breaches card network rules — surcharging where it is prohibited, for instance.
Yours, contractually and practically. We do not market to them, do not have a relationship with them, and do not appear in their app unless you choose to disclose the arrangement — and in some markets disclosure is required, which we will tell you about rather than leave you to discover.
That depends on the issuing partner's permissions and on your own licensing, and it is the first thing we establish in scoping. Anyone who answers «anywhere» to this question is either not a real provider or has not read their own agreement.
Often not, because the programme operates under the issuer's permissions — but it depends on what you do beyond issuing cards, and on the market. If your model requires you to be licensed, we will say so at scoping rather than after you have paid a setup fee.
REST APIs with webhooks, sandbox first. Create user, verify, issue card, set controls, read ledger, receive events. Teams that have integrated a payment API before find no surprises; teams that have not usually spend their time on the onboarding flow rather than on us.
There is a defined exit: your customers are notified, cards are wound down on a schedule rather than switched off, and balances are returned. An arrangement without a written exit is a hostage situation, and we would not sign one either.
Send Us Your Requirements
Markets, expected volume, timeline, and what you are building. We come back with a written proposal and an honest view of what is achievable in your timeframe.
- We tell you at scoping which markets and models we cannot support
- Commercial terms in writing, not a call to «discuss pricing»
- Sandbox access as soon as the programme is approved
