Skip to content
APIs/Payments/
Versioning and change log

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 to ensure a resilient integration.

Versioning log

New breaking versions of the API are listed here.

2024-06-01 (Latest)

Initial release

Use the value 2024-06-01 in the header parameter WP-Api-Version. See API Reference for details

Change log (non-breaking changes)

New features that are 'non-breaking' are listed below. For a robust integration please see our API principles.

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

More details

  • SCA exemptions in authentication
    You can now set an instruction.exemption.capability value of authenticationOnly or authorizationAndAuthentication to allow exemptions in authentication (3DS) to be returned. See details

  • 3DS support for encrypted Google Pay payments
    You can now use instruction.threeDS with encrypted Google Pay payments. PAN_ONLY (non Android device tokens) payments can now automatically be prompted for 3DS authentication. See details

  • Payment facilitator sub-merchant URL
    You can now send a 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.

  • Customer's ipAddress is now used in authorization
    We now use the instruction.customer.ipAddress key:value in the authorization process for Customer Initiated Transactions. Previously the value was only used for 3DS authentication.

Authentication outage (15 July 2025)

More details

We can now auto-apply an authenticationOutage exemption 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)

More details

  • Account updater support
    You can now request real-time account updates (Visa cards only) when using a previously stored 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 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)

More details

  • Co-branded card support
    You can now submit a preferredCardBrand value 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.

  • Sender date of birth for funds transfers (AFTs)
    You can now send the date of birth of the sender in your funds transfer (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)

More details

You can now send a fundsTransfer 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)

More details

You can now submit a Customer Initiated Transaction (CIT) using a Network Token provisioned by Worldpay without providing a cryptogram.

SCA exemptions in authorization (18 February 2025)

More details

You can now request SCA exemptions in authorization from Worldpay and have them automatically applied in the payment.

MOTO payments support (05 February 2025)

More details

You can now process Mail Order/Telephone Order payments by submitting "channel": "moto" key:value.

Payment facilitator support (28 January 2025)

More details

You can now facilitate transactions on behalf of your sub-merchants using the merchant.paymentFacilitator object.

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

More details

You can now set settlement.cancelOn.cvcNotMatched or settlement.cancelOn.avsNotMatched to disabled in auto settlement flow to prevent payment outcome of sentForCancellation.

2024

Network token support (21 November 2024)

More details

You can now submit a paymentInstrument.type of networkToken in a stored card flow. You must provide the paymentInstrument.cryptogram value as part of the request.

Installment and unscheduled MIT payments (17 October 2024)

More details

You can now setup installment plans 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.

You can now setup also unscheduled MIT agreements 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)

More details

We have documented code samples showing you how to integrate 3DS within a Payments API flow, in a React Native application.

Recurring subscription support (29 August 2024)

More details

You can now set up a subscription payment and make subsequent recurring payments. This includes a subscription agreement with no initial value (e.g. free trial).

Store a card only support (29 August 2024)

More details

You can now 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)

More details

You can specify threeDS.deviceData.channel 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)

More details

You can now provide, debtRepayment, consumerBillPayment and recipient information in your payment request