Request transaction matching
POST /v1/transaction-match
Submit transaction details for a single transaction to find a matching receipt when a PAR is not available. Each request matches one transaction — for ongoing automatic delivery, use a PAR subscription instead. Supply as many fields as possible — the more provided, the more accurate the match.
Authorizations
Section titled “Authorizations ”Request Body required
Section titled “Request Body required ”object
Freeform reference used for correlation in client system
Example
CUST-134422Date and time of the payment activity.
Example
2025-08-25T08:57:37+00:00object
Payment Account Reference (PAR) is 29 characters long. The first four positions of the PAR contain the BIN Controller Identifier. See: https://www.emvco.com/registered-ids
Example
12345678912345678912345678912RRN (ISO 8583 DE37). Preserve leading zeros.
Example
123456789012Acquirer Reference Number (ARN).
STAN, 6 digits.
Example
123456Transaction ID from bank, gateway, or store system.
Last four digits of the payment card.
Example
1234Approval code (AUTH).
Example
ABC123Terminal ID.
Terminal slip from the processor.
Monetary amount in a specific currency.
object
Amount of money, represented as a number with optional fractional part.
Example
19.99ISO 4217 three-letter currency code.
Example
USDResponses
Section titled “ Responses ”Transaction matching request received
Bad or malformed request
RFC 9457 problem details object.
object
A URI reference that identifies the problem type.
Short, human-readable summary of the problem type.
HTTP status code for this occurrence of the problem.
Human-readable explanation specific to this occurrence.
A URI reference that identifies the specific occurrence.
Unauthorized
RFC 9457 problem details object.
object
A URI reference that identifies the problem type.
Short, human-readable summary of the problem type.
HTTP status code for this occurrence of the problem.
Human-readable explanation specific to this occurrence.
A URI reference that identifies the specific occurrence.
Forbidden
RFC 9457 problem details object.
object
A URI reference that identifies the problem type.
Short, human-readable summary of the problem type.
HTTP status code for this occurrence of the problem.
Human-readable explanation specific to this occurrence.
A URI reference that identifies the specific occurrence.