Technical Description

#version 2.0.2 (30-08-2023)

-Add new v2.1 Id list call, returns a list of transactions instead of 0/1 transaction

  • /v2.1/acquirers/{acquirerId}/transactions/{transactionId}

    Note: In CNP the actionType CAPTURE_SPLIT can result in multiple cleared transactions with the same transactionId. In this unique case, please differentiate between transactions using the cleared transaction acquirerReferenceNumber and Capture request fields captureSequenceNumber, actionId.

-The status of the following v2.0 Id call has changed to deprecated, please use v2.1 call.

  • /v2.0/acquirers/{acquirerId}/transactions/{transactionId}

    Note: The above deprecated v2.0 call will remain available temporarily (up to 31-10-2024) allowing clients 6 months to migrate from current v2.0 Id call to v2.1.

-Changes to search call (/v2.0/acquirers/{acquirerId}/transactions)

  • Add query parameter actionId and pspReference
  • Rename query parameter merchantTransactionRefNo to merchantReference (old one still available but deprecated)

-Add 5 new fields in a transaction response: captureSequenceNumber, captureSequenceCount, schemeMerchantId, schemeTransactionId, paymentInitiationChannel

-Changes in TransactionIdentification (part of Transaction, Authorization and Lifecycle):

  • Rename field merchantTransactionReference to merchantReference (old field is deprecated, but still available up to 31-10-2024)
  • Add field actionId, pspReference, retrievalReferenceNumber

-Changes in ContractIdentification (part of Transaction, Authorization and Lifecycle)

  • Add field pspId

 

#version 2.0.1 (17-10-2022)

- Add 7 new fields to a transaction: result3ds, version3ds, cavv, xid, ucaf, mitCause, initiatorType

 

Version note:
Please be aware that these API interfaces may be changed and improved (e.g. addition of fields).

The "Try out" feature does not work at this time because the sandbox is being improved to support new functionality.