Cancel an authorisation using your reference

The three-character ISO currency code.

The amount of the transaction, in minor units.

In 3D Secure 1, the authentication response if the shopper was redirected.

In 3D Secure 2, this is the transStatus from the challenge result. If the transaction was frictionless, omit this parameter.

The cardholder authentication value (base64 encoded, 20 bytes in a decoded form).

The CAVV algorithm used. Include this only for 3D Secure 1.

In 3D Secure 1, this is the enrollment response from the 3D directory server.

In 3D Secure 2, this is the transStatus from the ARes.

Supported for 3D Secure 2. The unique transaction identifier assigned by the Directory Server (DS) to identify a single transaction.

The electronic commerce indicator.

The version of the 3D Secure protocol.

Supported for 3D Secure 1. The transaction identifier (Base64-encoded, 20 bytes in a decoded form).

The unique identifier of the account to which the split amount is booked. Required if type is MarketPlace or BalanceAccount.

• Classic Platforms integration: The accountCode of the account to which the split amount is booked.
• Balance Platform: The balanceAccountId of the account to which the split amount is booked.

The amount of the split item.

• Required for all split types in the Classic Platforms integration.
• Required if type is BalanceAccount, Commission, Default, or VAT in your Balance Platform integration.

Your description for the split item.

Your unique reference for the part of the payment booked to the specified account.

This is required if type is MarketPlace (Classic Platforms integration) or BalanceAccount (Balance Platform).

For the other types, we also recommend providing a unique reference so you can reconcile the split and the associated payment in the transaction overview and in the reports.

The part of the payment you want to book to the specified account.

Possible values for the Balance Platform:

• BalanceAccount: books part of the payment (specified in amount) to the specified account.
• Transaction fees types that you can book to the specified account:
  • AcquiringFees: the aggregated amount of the interchange and scheme fees.
  • PaymentFee: the aggregated amount of all transaction fees.
  • AdyenFees: the aggregated amount of Adyen's commission and markup fees.
  • AdyenCommission: the transaction fees due to Adyen under blended rates.
  • AdyenMarkup: the transaction fees due to Adyen under Interchange ++ pricing.
  • Interchange: the fees paid to the issuer for each payment made with the card network.
  • SchemeFee: the fees paid to the card scheme for using their network.
• Commission: your platform's commission on the payment (specified in amount), booked to your liable balance account.
• Remainder: the amount left over after a currency conversion, booked to the specified account.
• TopUp: allows you and your users to top up balance accounts using direct debit, card payments, or other payment methods.
• VAT: the value-added tax charged on the payment, booked to your platforms liable balance account.
• Commission: your platform's commission (specified in amount) on the payment, booked to your liable balance account.
• Default: in very specific use cases, allows you to book the specified amount to the specified account. For more information, contact Adyen support.

Possible values for the Classic Platforms integration: Commission, Default, MarketPlace, PaymentFee, VAT.