Skip to content
APIs/Payment Queries/
Versioning and change log

Versioning and change log

This log details any breaking and non-breaking API changes we have released for our Payment Queries API.

Prerequisite

Make yourself familiar with our API principles to ensure a resilient integration.

Versioning log

Version 1 (18 July 2024)

API Launch

Version 1 of the Payment Queries API launched.

Change log (non-breaking changes)

All non-breaking changes are recorded here.

Last event, command ID and payment ID now in response (17 October 2025)

More details

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.

Additional payment information (9 July 2025)

More details

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

Multi-entity support (18 November 2024)

More details

You can provide multiple entity references in date range queries to query payments based on entityReference (also known as entity).