**Last updated**: 07 April 2026 | [**Change log**](/access/products/payments/changelog/)

# Versioning and change log

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

Prerequisite
Make yourself familiar with our [API principles](/access/products/reference/api-principles) to ensure a resilient integration.

## Versioning log

New [breaking versions](/access/products/reference/api-principles#why-do-you-release-new-api-versions) of the API are listed here.

### `2024-06-01` (Latest)

details
summary
Initial release
Use the value `2024-06-01` in the header parameter `WP-Api-Version`. See [API Reference for details](/access/products/payments/openapi)

## Change log (non-breaking changes)

New features that are 'non-breaking' are listed below. For a robust integration please see our [API principles](/access/products/reference/api-principles#why-do-you-release-new-api-versions).

#### Support for tokenId in request (07 April 2026)

details
summary
More details
You can now provide [`tokenId` and, optionally, a `namespace`](/access/products/payments/openapi/payment/payment#payment/payment/t=request&path=instruction&d=0/paymentinstrument&d=1/tokenid) in your authorization request when using a `token` payment instrument.

Sending `tokenId` allows you to use a single global token across POS and e-commerce transactions without the need for token conversion between gateways.

Example use case: your customer signs up for a warranty in store, and makes subsequent recurring payments online.

#### Multiple features - including Agentic Commerce Protocol (ACP) support (18 February 2026)

details
summary
More details
* **Delegate tokens are now supported. Used as part of the Agentic Commerce Protocol (ACP) flow** 
Take payments via [ChatGPT (InstantCheckout/ACP - Agentic Commerce Protocol)](/access/products/ai/acp/) using a [delegate token](/access/products/payments/enable-features/acp-delegate-token/) created by Worldpay
* **Apple Pay and Google Pay Decrypted support** 
You can now provide [Google Pay decrypted](/access/products/payments/google-pay/) and [Apple Pay decrypted](/access/products/payments/apple-pay/) payment instruments.
* **FraudSight support for Google Pay and Apple Pay** 
[Google Pay](/access/products/payments/google-pay/) and [Apple Pay](/access/products/payments/apple-pay/) requests can now go through risk assessment using FraudSight.
* **AFT support for Apple Pay and Google Pay** 
[Google Pay](/access/products/payments/google-pay/) and [Apple Pay](/access/products/payments/apple-pay/) requests now support [AFT data](/access/products/payments/enable-features/account-funding-transactions/) to be provided as part of the request body.
* **`phone` and `email` used in payment authorization** 
We now also send `customer.phone` and `customer.email` as part of the payment authorization.
* **ipAddress provided for FraudSight risk assessment** 
We now also use the `customer.ipAddress` as part of a risk assessment using FraudSight.
* **Payment Facilitator support for zero value payments** 
We now use [Payment Facilitator](/access/products/payments/enable-features/payment-facilitator) data for [store a card only](/access/products/payments/store-card-only/) and [setup a recurring payment](/access/products/payments/recurring-first/) with no initial payment use cases.


#### Multiple features - including partial authorization and payment reversal (14 November 2025)

details
summary
More details
* **Partial authorization**
You can now enable partial authorization by setting the [`acceptPartialAuthorization` key:value](/access/products/payments/openapi/payment/payment#payment/payment/t=request&path=instruction&d=0/value/acceptpartialamount) to `true`. This allows you to accept a partial payment if the full amount is not available, and then charge the remaining balance using a different payment method through a new authorization request.
* **Payment reversal**
You can now [reverse a payment](/access/products/payments/openapi/manage-payments/reversal) using a new [next action link](/access/products/payments/openapi/payment/payment#payment/payment/t=response&c=201&path=&d=0/_actions/reversepayment) received in your authorization response.
* **Payment ID in responses**
We now return a [`paymentId` in the responses](/access/products/payments/openapi/payment/payment#payment/payment/t=response&c=201&path=&d=0/paymentid) on the following authorization outcomes: `authorized`, `refused`, `sentForSettlement`, `sentForCancellation`, `sentForRefund`, `sentForPartialRefund`.
The `paymentId` is a unique identifier for a payment that ties together payment lifecycle events.


#### Multiple features - including 3DS with encrypted Googlepay and SCA exemptions in authentication (29 October 2025)

details
summary
More details
* **SCA exemptions in authentication**
You can now set an [`instruction.exemption.capability`](/access/products/payments/openapi/payment/payment#payment/payment/t=request&path=instruction&d=0/exemption) value of `authenticationOnly` or `authorizationAndAuthentication` to allow exemptions in authentication (3DS) to be returned. [See details](/access/products/payments/enable-features/sca-exemptions/)
* **3DS support for encrypted Google Pay payments**
You can now use [`instruction.threeDS`](/access/products/payments/openapi/payment/payment#payment/payment/t=request&path=instruction&d=2/threeds) with encrypted Google Pay payments. `PAN_ONLY` (non Android device tokens) payments can now automatically be prompted for 3DS authentication. [See details](/access/products/payments/google-pay/)
* **Payment facilitator sub-merchant URL**
You can now send a [`merchant.paymentFacilitator.subMerchant.url`](/access/products/payments/openapi/payment/payment#payment/payment/t=request&path=merchant/paymentfacilitator/submerchant/url) key:value in your payment request. This allows you to be compliant with scheme requirements.
* **Additional 3DS outcome details in response**
We now include additional details on `3dsUnavailable` outcome in the response. This includes `eci` and `version`. See the [full response body](/access/products/payments/openapi/3ds-actions/supply3dsdevicedata#3ds-actions/supply3dsdevicedata/t=response&c=201&path=&d=0/threeds).
* **Customer's ipAddress is now used in authorization**
We now use the [`instruction.customer.ipAddress` key:value](/access/products/payments/openapi/payment/payment#payment/payment/t=request&path=instruction&d=0/customer/ipaddress) in the authorization process for Customer Initiated Transactions. Previously the value was only used for 3DS authentication.


#### Authentication outage (15 July 2025)

details
summary
More details
We can now auto-apply an [`authenticationOutage` exemption](/access/products/payments/openapi/payment/payment#payment/payment/t=response&c=201&path=&d=0/threeds) in authorization when we receive an `authenticationOutage` outcome from 3DS due to downstream issues (Visa/Mastercard etc).

This is currently not enabled by default, speak to your Implementation Manager to be set up for `authenticationOutage` responses.

#### Multiple features - including account updater support (25 June 2025)

details
summary
More details
* **Account updater support**
You can now request real-time account updates (Visa cards only) when using a [previously stored card](/access/products/payments/store-a-card) using `instruction.requestAccountUpdater`. If the supplied card has been updated, we will return updated card details in the `updatedPaymentInstrument` object in the authorization response.
* **`sequence` support in partial settle request**
You can now provide the [`sequence.number` and `sequence.total` key:values](/access/products/payments/openapi/manage-payments/partialsettle#manage-payments/partialsettle/t=request&path=sequence) in the partial settle request. This represents the sequence number and total number of expected partial settlement requests for the payment.
* **Relaxed email field validation to accept `"+"` character**
You can now provide email address values containing the `"+"` character in front of the `"@"` (e.g. `paymentsAPI+test@worldpay.com`).


#### Multiple features - including co-branded card support, Cartes Bancaires support and revenue boost indicator added (5 June 2025)

details
summary
More details
* **Co-branded card support**
You can now [submit a `preferredCardBrand` value](/access/products/payments/openapi/payment/payment#payment/payment/t=request&path=instruction&d=0/paymentinstrument&d=0/routing) allowing the transaction to be processed through either of its payment networks.
* **Cartes Bancaires support**
You can now submit a payment request using a Cartes Bancaires card brand.
* **Additional 3DS outcome details in response**
We now include additional details from the 3DS authentication in the response. This includes `eci`, `version`, `status` and `dsTransactionId`. See the [full response body](/access/products/payments/openapi/3ds-actions/supply3dsdevicedata#3ds-actions/supply3dsdevicedata/t=response&c=201&path=&d=0/threeds).
* **Sender date of birth for funds transfers (AFTs)**
You can now send the date of birth of the sender in your [funds transfer](/access/products/payments/openapi/payment/payment#payment/payment/t=request&path=instruction&d=0/fundstransfer/sender/dateofbirth) (AFT) requests. This is required for some cross border funding transactions.
* **Relax validation to support `moto` payments with a Checkout SDK session**
You can now send a `"channel": "moto"` payment request along with a `paymentInstrument.type` of `checkout`.
* **Revenue boost indicator added to response**
`updatedPaymentInstrument.appliedNetworkToken` is set to `true` when a network token is automatically applied


#### Account Funds Transfers (AFTs) (03 April 2025)

details
summary
More details
You can now send a [`fundsTransfer`](/access/products/payments/openapi/payment) object in your payment requests. This unlocks the ability to process AFTs compliant with card scheme requirements. AFTs are used to transfer funds from a card account to another destination, rather than for the provision of goods or services.

#### Auto-provision cryptogram for NPTs created through Worldpay systems (26 March 2025)

details
summary
More details
You can now submit a Customer Initiated Transaction (CIT) using a Network Token provisioned by Worldpay [without providing a `cryptogram`](/access/products/payments/openapi/payment).

#### SCA exemptions in authorization (18 February 2025)

details
summary
More details
You can now request [SCA exemptions in authorization](/access/products/payments/enable-features/sca-exemptions/) from Worldpay and have them automatically applied in the payment.

#### MOTO payments support (05 February 2025)

details
summary
More details
You can now process Mail Order/Telephone Order payments by submitting [`"channel": "moto"` key:value](/access/products/payments/enable-features/moto/).

#### Payment facilitator support (28 January 2025)

details
summary
More details
You can now facilitate transactions on behalf of your sub-merchants using [the `merchant.paymentFacilitator` object](/access/products/payments/enable-features/payment-facilitator/).

#### Disable automatic `sentForCancellation` outcome based on CVC/AVS (17 January 2025)

details
summary
More details
You can now set `settlement.cancelOn.cvcNotMatched` or `settlement.cancelOn.avsNotMatched` to `disabled` in [auto settlement](/access/products/payments/enable-features/auto-settlement/) flow to prevent payment outcome of `sentForCancellation`.

details
summary
2024
#### Network token support (21 November 2024)

details
summary
More details
You can now submit a `paymentInstrument.type` of `networkToken` in a [stored card](/access/products/payments/use-a-stored-card/) flow. You must provide the `paymentInstrument.cryptogram` value as part of the request.

#### Installment and unscheduled MIT payments (17 October 2024)

details
summary
More details
You can now setup [installment plans](/access/products/payments/recurring-first/) by submitting a `customerAgreement.type` of `installment`. A typical use case would be, to spread the cost of a larger payment over time. Additionally, this unlocks installment payments in [Latin America](/access/products/payments/enable-features/latam-installments/).

You can now setup also [unscheduled MIT agreements](/access/products/payments/recurring-subsequent/) by submitting a `customerAgreement.type` of `unscheduled`. A typical use case for this, might be an automatic top-up when the account value falls below a threshold.

#### React Native support (08 October 2024)

details
summary
More details
We have documented [code samples](/access/products/payments/enable-features/3ds-authentication/react-native/) showing you how to integrate 3DS within a Payments API flow, in a React Native application.

#### Recurring subscription support (29 August 2024)

details
summary
More details
You can now [set up a subscription payment](/access/products/payments/recurring-first) and make [subsequent recurring payments](/access/products/payments/recurring-subsequent). This includes a subscription agreement with no initial value (e.g. free trial).

#### Store a card only support (29 August 2024)

details
summary
More details
You can now [store a card](/access/products/payments/store-a-card) for future Customer Initiated Transactions (CITs) without an initial payment. You can use this for adding a card to an ecommerce account.

#### 3DS deviceData channel (29 August 2024)

details
summary
More details
You can specify [threeDS.deviceData.channel](/access/products/payments/enable-features/3ds-authentication#emvco-required-values) as `browser` to indicate the integration for web or native for iOS/Android. We strongly recommend you provide this to keep authentication rates as high as possible.

#### Financial Services MCC6012 support (22 July 2024)

details
summary
More details
You can now provide, `debtRepayment`, `consumerBillPayment` and `recipient` information in your [payment request](/access/products/payments/enable-features/financial-services-mcc6012-mcc6051)