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 API Principles

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