Versioning and change log

Version 1 of the Payment Queries API launched.

• You can now query orders by orderReference. This query returns data for payments processed after 20 August 2026.

• You now receive a fpanLastFour in your response when querying by transactionReference and retrieving a payment using the paymentId. This helps you to identify which physical card your customer used in a digital wallet (e.g. Apple Pay or Google Pay) or network token payment.

• You now also receive a token object when retrieving a payment by paymentId for mobile wallet payments made using our modular Card Payments API.

You now receive a lastEvent in your response when querying by transactionReference and retrieving a payment using the paymentId.
You now also receive a commandId when retrieving a payment by paymentId.

We now also include the paymentId in all responses.

We now return the following additional payment information for queries by date range, queries by transaction reference, and retrieving a single payment, where this information is returned in your card payment authorization response:

• scheme.reference
• issuer.authorizationCode
• paymentInstrument.card.number.cardBin
• paymentInstrument.card.category
• paymentInstrument.card.expiryDate
• paymentInstrument.card.countryCode
• paymentInstrument.card.issuerName
• paymentInstrument.card.paymentAccountReference
• updatedPaymentInstrument