Modifications

Capture an authorisation

Captures the authorisation hold on a payment, returning a unique reference for this request. Usually the full authorisation amount is captured, however it's also possible to capture a smaller amount, which results in cancelling the remaining authorisation balance.

Payment methods that are captured automatically after authorisation don't need to be captured. However, submitting a capture request on these transactions will not result in double charges. If immediate or delayed auto-capture is enabled, calling the capture method is not necessary.

For more information refer to Capture.

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}/captures endpoint 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.

post/capture

Request body

additionalDataobject

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.

merchantAccountstring required

The merchant account that is used to process the payment.

originalReferencestring required

The original pspReference of the payment to modify. This reference is returned in:

authorisation response
authorisation notification

referencestring

Your reference for the payment modification. This reference is visible in Customer Area and in reports. Maximum length: 80 characters.

tenderReferencestring

The transaction reference provided by the PED. For point-of-sale integrations only.

uniqueTerminalIdstring

Unique terminal ID for the PED that originally processed the request. For point-of-sale integrations only.

Response

OK - the request has succeeded.

additionalDataobject

This field contains additional data, which may be returned in a particular modification response.

pspReferencestring required

Adyen's 16-character string reference associated with the transaction/request. This value is globally unique; quote it when communicating with us about this request.

Indicates if the modification request has been received for processing.

Changes

Changed in 4 of the 51 revisions of this API.1633

Feb 17, 2026v2520c98153769d2See the full diff
- ●
  added the new Error enum value to the response property for the response status
  response-property-enum-value-added
- ●
  added the new Refused enum value to the response property for the response status
  response-property-enum-value-added
Oct 21, 2024v2527588197cceb1See the full diff
- ●
  added the new Authorised enum value to the response property for the response status
  response-property-enum-value-added
Feb 24, 2023v256522ce018f708See the full diff
- ▲
  the request's body type changed from no type to object
  request-body-type-changed
- ▲
  the request property type changed from no type to object
  request-property-type-changed
- ▲
  the response's body type changed from no type to object for status
  response-body-type-changed
- ▲
  the response's body type changed from no type to object for status
  response-body-type-changed
- ▲
  the response's body type changed from no type to object for status
  response-body-type-changed
- ▲
  the response's body type changed from no type to object for status
  response-body-type-changed
- ▲
  the response's body type changed from no type to object for status
  response-body-type-changed
- ▲
  the response's body type changed from no type to object for status
  response-body-type-changed
Dec 5, 2022v25da6633eb75e183See the full diff
- ▲
  the request's body type changed from object to no type
  request-body-type-changed
- ▲
  the request property type changed from object to no type
  request-property-type-changed
- ▲
  the response's body type changed from object to no type for status
  response-body-type-changed
- ▲
  the response's body type changed from object to no type for status
  response-body-type-changed
- ▲
  the response's body type changed from object to no type for status
  response-body-type-changed
- ▲
  the response's body type changed from object to no type for status
  response-body-type-changed
- ▲
  the response's body type changed from object to no type for status
  response-body-type-changed
- ▲
  the response's body type changed from object to no type for status
  response-body-type-changed
- ○
  removed the Authorised enum value from the response property for the response status
  response-property-enum-value-removed
- ○
  removed the Error enum value from the response property for the response status
  response-property-enum-value-removed
- ○
  removed the Refused enum value from the response property for the response status
  response-property-enum-value-removed
This revision also has 3 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Full history