Issuing
One rail. Physical, virtual, wallet.
Issue across schemes, manage BIN sponsorship, ship card programs in weeks — backed by 20+ years of payment-grade ops.
Form factors
Program & ops services
- BIN sponsorship through bank partners (region-dependent)
- Tokenization and 3DS-out for issuer-side authentication
- Authorization stand-in, velocity and risk rules
- Program management ops — disputes, fraud monitoring, reconciliation
Issue a virtual card in one call
# Issue a virtual card under an existing program
curl -X POST https://api.coshine.com/v1/cards \
-H "Authorization: Bearer $COSHINE_TOKEN" \
-H "X-Timestamp: $(date +%s)" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{
"program_id": "prog_vc_sgd",
"type": "virtual",
"cardholder_ref": "cust_4f9a",
"initial_load": { "amount": 0, "currency": "SGD" }
}'
# 201 Created
{
"id": "card_8h2k3l",
"status": "active",
"pan_last4": "4242",
"expiry": "2030-12",
"network_token": { "scheme": "MASTERCARD", "id": "tk_9p3a..." }
}Typical timeline to first live card
Week 0 — Discovery
Scope the program: BIN range, scheme, geographies, cardholder population, expected volume, dispute model. Bank sponsorship arrangement confirmed.
Week 1–2 — Sandbox & integration kick-off
Sandbox keys, sample programs and test card sets provisioned. Integration team starts building against the live API; webhooks subscribed in test.
Week 3–6 — Build & internal test
Cardholder onboarding, lifecycle hooks, settlement and reporting integration completed. Internal end-to-end runs against sandbox data.
Week 7–10 — Scheme certification & rehearsal
Scheme certification scripts executed and signed off. Operational rehearsal with the bank's ops team — disputes, fraud, reissue, lost / stolen.
Week 11+ — Pilot launch
Phased production launch: pilot cohort first, then volume ramp on a published schedule. Joint daily standups for the first two weeks of live traffic.
Program specifications
| Capability | Coverage |
|---|---|
| Card types | Credit · Debit · Prepaid · Virtual |
| Schemes | Visa · Mastercard · UnionPay · JCB · Amex (per BIN) |
| Form factors | Plastic · Metal · Virtual · Tokenized (Apple Pay, Google Pay, network tokens) |
| Settlement currencies | USD · EUR · SGD · HKD · JPY · CNY · MYR · IDR · THB · VND · PHP · AUD · GBP · KRW (and more on request) |
| Authentication | EMV 3-D Secure 2.x with risk-based and OOB flows |
| BIN model | Bring-your-own BIN, or use a sponsor bank in the region |
| Personalization | Bulk and on-demand; multiple in-region fulfillment partners |
| Operational scope | Authorization, clearing, billing, settlement, dispute — under one program |
Frequently asked
Can we bring our own BIN, or do we need sponsorship?
Both are supported. Banks with their own scheme membership bring their own BIN; FinTechs without principal-member status partner with one of our sponsor banks — sponsorship is region-specific and we'll match you to a partner during scoping.
How fast from contract to first live card?
Eleven weeks is the standard plan for a new program on an existing BIN; longer if a new BIN range needs to be applied for or if a new sponsor relationship is being set up. Re-launches against an existing program are faster.
Apple Pay / Google Pay / network tokens — supported?
Yes. We provision network tokens via Visa Token Service and Mastercard MDES at card issuance, so cardholders can add the card to wallets without re-typing PAN. Provisioning is scoped per scheme and per region.
How do chargebacks work on the issuing side?
Cardholders raise disputes through the issuing bank's channel; the platform routes them through the dispute lifecycle (representment, pre-arbitration, arbitration) per scheme rules. We provide the case files, the timelines and the workflow tooling; the issuer makes the credit/debit decision.
Do you support PIN and card-present transactions?
Yes. PIN issuance is supported under PCI PIN scope; card-present authorization works alongside CNP under the same authorization endpoint. PIN issuance topology (online vs offline, scheme-specific) is scoped during program design.