Programme model
Crypto wallets
Add everyday spending to an existing wallet relationship without forcing customers into a separate product.
Wallet syncCardsConversion
Crypto cards
Turn digital asset balances into a controlled card experience.
Connect wallet availability, conversion, authorisation, ledger posting and card controls so customers can spend through a product that remains understandable to operations and compliance teams.
Wallet-aware spend decisions
Fiat and digital asset ledger context
Virtual and physical card lifecycle
Configurable risk and spending controls
A card product in your brand
YOUR BRANDVIRTUAL
•••• 4829
ALEX MORGANcard
Controls in context
Manage a card in the same product your customer uses.
Connected balance
Tie card spend to account or wallet availability.
Card lifecycle
1. IssueCreate the right card form for the customer journey.
2. FundConnect availability to an account or wallet balance.
3. ControlApply permissions that reflect your spend model.
4. ManageHandle the card experience from your own product.
Programme design
A card should express your product — not become a separate product.
A reliable crypto card workflow needs a consistent view of available funds, pricing, authorisation, holds, reversals and final settlement. Framnex keeps these states connected instead of treating the card processor as the entire product.
Card availability, supported assets, conversion model and programme responsibilities depend on geography, partners and customer type.
Programme model
Exchanges and trading platforms
Extend a trading relationship into a controlled branded spend proposition.
BalancesCardsRisk controls
Programme model
Stablecoin products
Use stablecoin availability as part of a fiat card and settlement workflow.
StablecoinsLedgerSettlement
Capabilities
Build the card programme around the controls your model requires.
Choose the components that solve the immediate customer need, with the option to connect more services as the product grows.
Wallet balance connectivity
Connect spend decisions to the relevant custodial or platform balance and its availability rules.
Conversion logic
Define when and how digital assets are converted to the settlement currency, including pricing and fallback behaviour.
Card lifecycle
Support provisioning, activation, controls, suspension and replacement for virtual or physical cards.
Risk and reconciliation
Link authorisations, captures, reversals, fees and settlement records to an auditable ledger trail.
Authorisation flow
Make a spend decision with enough context to protect the customer and the programme.
The response path needs to coordinate several systems without losing a single source of truth.
01
Receive the card event
Capture amount, currency, merchant context and programme rules from the processor.
02
Check eligible availability
Evaluate wallet balance, asset rules, pending activity and customer controls.
03
Apply pricing and risk
Quote or reserve the conversion while fraud, velocity and compliance rules run.
04
Post and reconcile
Record the hold, capture, fees, conversion and settlement with linked references.
Cardholder experience
Turn a card into a visible expression of your product.
Pair a branded virtual or physical card with the in-product controls and balance context that make it useful.
Launch path
Start with a clear first workflow.
A focused launch makes it easier to align commercial owners, operations and product teams before adding more complexity.
- 1Choose the spend sourceDefine which wallet, asset and availability state can support a card authorisation.
- 2Design the conversion modelSet pricing, timing, fallback and treasury assumptions before card rules are configured.
- 3Connect authorisation and ledger eventsEnsure holds, captures, reversals and fees create consistent financial records.
- 4Pilot with controlled limitsStart with a clear customer segment, supported assets and risk limits before expanding.
Crypto cards FAQ
Questions about this solution.
The commercial and operational questions teams most often ask before outlining their first launch.
Does a customer need to preload a fiat balance?
That depends on the programme design. Some models use a fiat or stablecoin buffer; others evaluate an eligible wallet balance and conversion path during authorisation.
Which digital assets can be supported?
The supported asset set is defined by custody, liquidity, risk and programme partners. A focused initial list is normally easier to operate and reconcile.
Does Framnex provide the card network directly?
Framnex coordinates the product and integration layer around relevant issuing, processing and programme partners. The final partner structure depends on the market and use case.
How are risk and compliance controls applied?
Customer, wallet and transaction controls are designed into onboarding, authorisation and ongoing monitoring. Exact responsibilities are defined in the operating model.
Start with a discovery call
Ready to explore what's possible?
In a 15-minute discovery session, we'll discuss your business model, customer needs and commercial objectives to determine the right foundation for your financial offering.
No technical preparation required
Business-focused discussion
Tailored recommendations
No obligation