Developer & API
Oct 13, 2025
Developer API We Tokenised a $25M Property Portfolio in 90 Days
SHARE THIS ARTICLE
Launching a modern card program = the right license (via BIN sponsor), airtight KYC/AML, strong auth & controls, and clear ops (disputes, fraud, settlement). This guide gives you the moving parts, an architecture you can copy, and a 30-day launch checklist.
Why card issuing still matters
Cards are the most universally accepted payment form. For fintechs, they’re a growth lever: instant activation, rich data, and programmable controls that tie directly to product value (rewards, expense policies, marketplace payouts).
Key terms (quick primer)
Issuer: The licensed bank/entity that “issues” the card.
BIN (Bank Identification Number): The 6–8 digits that route transactions to your issuer.
BIN Sponsorship: A licensed issuer lets you run a program on their BIN, under their compliance umbrella.
Program Manager: You (or your partner) who designs features, KYC, controls, and ops.
Processor: Tech layer handling authorisations, tokenisation, settlement files, disputes.
Network: Visa/Mastercard etc.
Card Controls: Rules at auth time (MCC blocks, limits, geofencing, merchant allow/deny).
The building blocks
Licensing via BIN sponsorship
You don’t need to become a bank. A sponsor issuer provides:
Access to card networks and their BINs
Compliance governance (& policy reviews)
Settlement accounts and scheme reporting
What you own: product experience, KYC/KYB, card controls, fraud rules, support, and your processor integration.
Compliance & KYC/KYB
CDD/KYC: identity, sanctions/PEP screening, liveness checks
KYB (for business cards): UBOs, company registry checks, sanctions
Ongoing monitoring: velocity anomalies, device risk, chargeback ratio
Real-time authorisation flow
Card present/online purchase hits the network
Network routes to processor on your BIN
Processor calls your Auth API with transaction context
Your service evaluates controls + balance + risk
Approve/decline with reason codes; log event; update ledger
Post-auth notifications, webhooks, receipts, and analytics
Conclusion
Card issuing isn’t just about printing plastic—it’s a programmable rail you can shape with policy, risk, and UX. Start under a BIN sponsor, centralise a Controls Engine for real-time decisions, and build recon + dispute ops from day one. If you can keep approval rates high while reducing fraud and chargebacks, the unit economics work—and you get a defensible product edge.
Mark Wazowski
Copywriting
Independent audit partners
