Skip to main content
The Issuer API lets card issuers integrate directly with OpenCard and distribute transaction data to connected Expense Management Systems (EMS). In addition to standard transaction data, OpenCard can attach enriched information — digital receipts, correct VAT, line items, environmental metrics — through partner networks. EMS users get a fuller picture of each purchase without you building that layer yourself.
This is not the digital receipts API on receipts.opencard.io. That is a separate product for receipt matching only. See Digital receipts if you need it.

​
Before you integrate

  1. Customer signs a TPA (Transaction Processing Authorisation) via their EMS — authorising the issuer to release that company’s card data to OpenCard.
  2. OpenCard delivers your credentials — OAuth client, scopes, and your issuer {slug}.
  3. You register cards — OpenCard needs an up-to-date card registry per customer organisation.
  4. You push transaction states — authorized, cleared, invoiced, and deleted for every purchase.
Until cards exist and states are delivered, EMS apps connected to that customer will not receive data.

​
End-to-end flow

​
API surface

All endpoints live under:
Replace {slug} with the value OpenCard assigns your integration (e.g. your program’s short name). The boilerplate reference implementation uses this path pattern — your deployment may add or omit endpoints; confirm with OpenCard before go-live.

​
Guides

API reference → Issuer API

​
Environments

Contact support@opencard.io to start integration and receive sandbox credentials.