# 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](/products/reference/api-principles) to ensure a resilient integration.

## Versioning log

#### Version 1 (18 July 2024)

details
summary
API Launch
Version 1 of the Payment Queries API launched.

## Change log (non-breaking changes)

All non-breaking changes are recorded here.

#### Multiple features - including query by orderReference (26 August 2026)

details
summary
More details
- You can now [query orders by `orderReference`](/products/payment-queries/openapi/other/querybydaterange#other/querybydaterange/t=request&in=query&path=orderreference). This query returns data for payments processed after 20 August 2026.
- You now receive a [`fpanLastFour`](/products/payment-queries/openapi/other/retrievebypaymentid#other/retrievebypaymentid/t=response&c=200&path=paymentinstrument/card/number/fpanlastfour) in your response when [querying by `transactionReference`](/products/payment-queries/openapi/other/querybydaterange#other/querybydaterange/t=request&in=query&path=transactionreference) and [retrieving a payment](/products/payment-queries/openapi/other/retrievebypaymentid) 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`](/products/payment-queries/openapi/other/retrievebypaymentid#other/retrievebypaymentid/t=response&c=200&path=token) object when [retrieving a payment](/products/payment-queries/openapi/other/retrievebypaymentid) by `paymentId` for mobile wallet payments made using our modular [Card Payments API](/products/card-payments/openapi/other/authorize).


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

details
summary
More details
You now receive a [`lastEvent`](/products/payment-queries/openapi/other/retrievebypaymentid#other/retrievebypaymentid/t=response&c=200&path=lastevent) in your response when [querying by `transactionReference`](/products/payment-queries/openapi/other/querybydaterange#other/querybydaterange/t=request&in=query&path=transactionreference) and [retrieving a payment](/products/payment-queries/openapi/other/retrievebypaymentid) using the `paymentId`. 
You now also receive a `commandId` when [retrieving a payment](/products/payment-queries/openapi/other/retrievebypaymentid) by `paymentId`.

We now also include the `paymentId` in all responses.

#### Additional payment information (9 July 2025)

details
summary
More details
We now return the following additional payment information for [queries by date range](/products/payment-queries/query-by-date-range), [queries by transaction reference](/products/payment-queries/query-by-trans-ref), and [retrieving a single payment](/products/payment-queries/retrieve-by-payment-id), 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`


details
summary
2024
#### Multi-entity support (18 November 2024)

details
summary
More details
You can provide [multiple entity references in date range queries](/products/payment-queries/query-by-date-range) to query payments based on `entityReference` (also known as `entity`).