A card bank under your brand.
Live in a week
The full crypto-card stack — Visa issuing, KYC, a double-entry ledger, webhooks and a ready front-end — as a service. You integrate over REST, brand it and sell cards to your users. Compliance, the banking integration and accounting are our side.
< 7 days
from API key to live card
our first partner's path
2 + 1
brands on the engine
Libermall, Tegro + external partner
15+
REST endpoints
the full card lifecycle
$0
setup fee
pay for operations only
How it's built
One API covers the whole path — from cardholder KYC to card transactions. Your product is the top layer; everything beneath it already runs in production.
YOUR SIDE
- Your brand & app
- Your users
- Your pricing & margin
OUR ENGINE
- REST /api/v1 + webhooks
- KYC pipeline
- Double-entry ledger + float
- Issuing & card operations
- Reconciliation & monitoring
PARTNER BANK
- Visa issuing
- Processing
- Apple Pay / Google Pay
Building in-house vs white-label
| From scratch | On our engine | |
|---|---|---|
| Time to launch | 6–12 months | about a week |
| Team | backend, compliance, fin-ops | 1 engineer |
| Banking integration | source and pass it yourself | signed and live |
| KYC stack | own vendor + procedures | included, statuses via webhooks |
| Accounting | build a ledger yourself | double-entry + daily reconciliation |
| Upfront investment | $100k+ | $0 setup, prepaid float |
Partner economics
You set retail prices on top of our cost — margin on issuance, top-ups and FX is yours. An illustrative model (cost basis is fixed in the agreement):
| Scenario | Cards / mo | Partner revenue* | Your margin |
|---|---|---|---|
| Start | 100 | $500–1,000 | issuance markup |
| Growth | 1,000 | $8k–15k | + top-up fees |
| Scale | 10,000 | $80k+ | + FX spread & subscriptions |
*example: $5–10 retail issuance over cost from $2.5; 1–3% top-up fees; retail pricing is your call.
Integration
A REST API with idempotency on every mutation, HMAC-signed webhooks with retries, and polling backstops for missed events. Sandbox access before any agreement.
Endpoints
POST /v1/cardholdersGET /v1/cardholders/{id}POST /v1/kyc/sessionsGET /v1/kyc/sessions/{id}GET /v1/productsPOST /v1/cardsGET /v1/cards/{id}POST /v1/cards/{id}/loadPOST /v1/cards/{id}/freezePOST /v1/cards/{id}/unfreezePOST /v1/cards/{id}/closePOST /v1/cards/{id}/set-pinGET /v1/cards/{id}/transactionsGET /v1/cards/{id}/secure-detailsGET /v1/balancePOST /v1/balance/topupsGET /v1/eventsWebhooks
card.issuedcard.status_changedcard.transactionkyc.updatedbalance.creditedfee.chargedIssue a card — one request
curl -X POST https://card.libermall.com/api/v1/cards \
-H "Authorization: Bearer lmc_sk_live_..." \
-H "Idempotency-Key: 9f3a-…" \
-d '{
"cardholderId": "ch_8Ki2…",
"product": "virtual-usd",
"card_name": "Ads · Meta",
"client_ref": "user-42"
}'OpenAPI spec, docs and examples: cardos.dev/docs · github.com/Libermall
Launch timeline
Day 0
Start in CardOS
sign up in the cardos.dev builder — bot and cards with no code, instantly
Day 1
Access
API key, sandbox, webhook secret
Days 2–4
Integration
KYC → issue → load → webhooks
Day 5
Float & dry run
fund the balance, control cards
Days 6–7
Go-live
production issuance to your users
Live in production
FAQ
What do we need to launch?
A partner agreement, an API key and a prepaid float — the balance your users' issues and loads draw from. Funded in USDT (TRC-20/TON), debited in real time, every operation visible in the ledger.
Who handles KYC and the data?
Cardholder KYC runs through our pipeline with the partner bank: you send holder data via API and receive status webhooks. No compliance stack needed on your side.
Which cards and currencies?
Virtual Visa and Mastercard, USD balances (internal 1USDT pegged 1:1). Apple Pay / Google Pay and 3D Secure products are separate SKUs (holder KYC); the full list with BIN, scheme and issuing country comes from GET /v1/products. Subscriptions, services and purchases worldwide.
How is pricing formed?
Operation cost plus a partner margin, fixed in the agreement and volume-dependent. No setup fee. Retail prices for your users are yours to set.
How reliable is it?
Idempotency on every mutation (a retried request never double-executes), signed webhooks with retries, polling backstops, daily float spend caps and automatic bank reconciliation — the same stack serves our own brands.
Can we launch without our own app?
Yes: a white-label version of our Telegram Mini App and web cabinet with your theme. Your brand and pricing — our interface.
Who supports the end users?
First line — you (they are your customers); infrastructure incidents and the bank — us. SLA and the escalation matrix live in the agreement.
Which networks fund the float?
USDT over TRC-20 and TON — credited automatically, the balance is instantly visible in the ledger and via GET /v1/balance. Every spend operation is tied to a specific card and holder.
Can one user hold several cards?
Yes — a single holder can have several cards for different tasks, within the card program's limits. Available products, including BIN, scheme and issuing country, are returned by GET /v1/products.
Can the whole user journey stay inside our interface?
Yes: holder registration, issuing, top-ups and card management run through the API inside your product. KYC runs in the bank's hosted widget via a link from the API (POST /v1/kyc/sessions → hosted_url), the status arrives by webhook and the user returns to your product. Card details are shown via the engine's secure reveal, so the PAN never transits your backend and no PCI burden lands on you.
Is there volume pricing?
Yes. Operation costs go down as card count and volume grow, fixed in the agreement. Retail prices always remain yours.
Can we get the BIN list, limits and a sample agreement?
Yes — as a pack on request under NDA: the BIN list with issuing countries, card limits, KYB requirements and B2B terms. Write to [email protected] or @YouLibermallbot.
Where do we start?
Fastest path — the CardOS builder (cardos.dev): a branded card bot with no code, live right away. For a deep API integration into your own product or custom volumes — Telegram or [email protected].
Ready to launch your cards?
Self-serve in the CardOS builder — start right now, no agreement, no setup fee. For enterprise API integrations — write to us.
Open the CardOS builderEnterprise: t.me/YouLibermallbot · [email protected]