receipts.opencard.io.
Step 1: Discover merchants
Step 2: Submit transaction for matching
Required transaction fields
| Field | ISO8583 | Description |
|---|---|---|
id | — | Your public transaction ID |
auth_date | Field 13 | YYYY-MM-DD |
auth_time | Field 12 | HH:mm:ss |
auth_timezone | — | e.g. Europe/Stockholm |
reference_no | Field 37 | Retrieval reference number |
auth_code | Field 38 | Authorization code |
terminal_id | Field 41 | Terminal ID |
merchant_no | Field 42 | Merchant ID (CAID) |
merchant_name | Field 43 | Merchant name |
auth_amount | — | Original amount |
auth_currency | — | ISO 4217 |
auth_masked_card_number | — | Masked PAN |
clearing | — | "true" / "false" |
Step 3: Receive matched receipt
OpenCard calls yourcallback_path when a receipt is matched. Your endpoint must:
- Accept the configured
callback_content_type - Return HTTP
200 - Verify webhook signature (provided during onboarding)
Update when transaction clears
clearing to "true" when the transaction settles — improves match accuracy.

