PaymentsCards & Services
Virtual cards
Cobru card issuance and card operations surface.
The cards family is backed by legacy Cobru exports rather than a freshly verified public contract. The endpoint surface is meaningful, but you should still validate issuer behavior, PCI scope, and operational states before launch.
Cobru's API menu includes a Tarjetas section, indicating a broader programmable cards
capability layered on top of the wallet and balance infrastructure.
Choose a card workflow
Create or top up
Issue a virtual card or add balance using the combined create-and-reload surface.
Inspect cards
Retrieve card metadata and existing cards when support or operations need visibility.
Review movements
Inspect transactions for reconciliation, risk review, and support investigation.
Freeze card
Stop or resume card usage as part of operational controls.
Visible operations
| Operation | Method | Path | Confidence |
|---|---|---|---|
| Create card | POST | /cobru/debit/create_and_reload_card/ | legacy-doc |
| Top up card | POST | /cobru/debit/create_and_reload_card/ | legacy-doc |
| Card details and list | GET | /cobru/debit/get_card/ | legacy-doc |
| Movements | GET | /cobru/debit/get_transactions/ | legacy-doc |
| Freeze card | POST | /cobru/debit/freeze_card/ | legacy-doc |
Launch constraints
- confirm issuer SLA and operational ownership before enabling cards for customers
- map PCI, PII, and support access rules before exposing card data in internal tooling
- treat freeze and unfreeze as high-sensitivity actions with audit logs