Change the authorised amount
Allows you to increase or decrease the authorised amount after the initial authorisation has taken place. This functionality enables for example tipping, improving the chances your authorisation will be valid, or charging the shopper when they have already left the merchant premises.
This endpoint is inactive and is no longer supported for new integrations.
- If you are building a new integration, use the Checkout API
/payments/{paymentPspReference}/amountUpdatesendpoint instead.- If you have an existing integration using this endpoint, reach out to your Adyen contact and migrate to the Checkout API.
The Checkout API enables your online payments integration to accept all supported payment methods, use the latest features, and access more benefits.
This field contains additional data, which may be required for a particular modification request.
The additionalData object consists of entries, each of which includes the key and value.
The merchant account that is used to process the payment.
The currency and value of the new total amount in minor units. For example, to increase the amount, the value is the sum of the pre-authorized amount and the additional amount.
Authentication data produced by an MPI (Mastercard SecureCode, Visa Secure, or Cartes Bancaires).
The original merchant reference to cancel.
The original pspReference of the payment to modify. This reference is returned in:
- authorisation response
- authorisation notification
Your reference for the payment modification. This reference is visible in Customer Area and in reports. Maximum length: 80 characters.
An array of objects specifying how the amount should be split between accounts when using Adyen for Platforms. For more information, see how to split payments for platforms.
The transaction reference provided by the PED. For point-of-sale integrations only.
Unique terminal ID for the PED that originally processed the request. For point-of-sale integrations only.
After submitting a call, you receive a response message to inform you that your request was received and processed.
Depending on the HTTP status code of the response message, it is helpful to build some logic to handle any errors that a request or the system may return.
HTTP Responses
200 - OK
The request has succeeded.
400 - Bad Request
A problem reading or understanding the request.
401 - Unauthorized
Authentication required.
403 - Forbidden
Insufficient permissions to process the request.
422 - Unprocessable Entity
A request validation error.
500 - Internal Server Error
The server could not process the request.