Are you looking for test card numbers?

Would you like to contact support?

Default icon


Complete an authorised payment.

Capture in Customer Area

You can also capture payments in your Customer Area. For more information, refer to Manage payments.

For some payment methods, the payment is completed in two steps:

  1. Authorisation: The payment details of the shopper are verified with the issuer, and the funds are reserved.
  2. Capture: The reserved funds are transferred from the shopper to your account.

By default, payments are captured automatically, immediately after authorisation.

For payment methods that support separate authorisation and capture, you can also capture the payment later, for example after the goods have been shipped. This allows you to cancel the payment in case of any issues with the shipment.

To learn if a payment method supports separate captures, refer to the payment method page such as Cards or Klarna.

To capture payments, you can use:

Automatic capture

With automatic capture, payments are captured automatically, using the capture delay that you specify.

Capture delay

By default, payments are captured immediately after authorisation. Setting up a delay between the authorisation and the automatic capture of the payment allows you to cancel the authorisation, for example when it turns out that an item is out of stock.

To be able to change capture settings, you need to have the following user role:

  • Merchant admin

To set up a capture delay:

  1. Log in to your Customer Area.
  2. Switch to your merchant account.
  3. Go to Settings > Account settings.
  4. In the Capture Delay dropdown list, select the capture delay that you want to use. Possible values:
    • immediate: capture happens immediately after authorisation.
    • [N] days: capture happens N (between 1 and 7) days after authorisation.
  5. Select Submit.

A payment that is automatically captured does not trigger a separate CAPTURE notification webhook. If you are using delayed automatic capture, you can optionally receive CAPTURE webhooks. To enable this functionality, contact our Support Team.

Manual capture

With manual capture, you need to explicitly request a capture for each payment.

To be able to change the capture settings, you need to have the following user role:

  • Merchant admin

To enable manual capture:

  1. Log in to your Customer Area.
  2. Switch your merchant account.
  3. Go to Settings > Account settings.
  4. In the Capture Delay list, select manual.
  5. Select Submit.

Once you've enabled manual capture, you need to capture each payment by making an API request.

Alternatively, you can include in your payment request captureDelayHours, specifying a number of hours after which the payment will be captured.

For example, to have the payment captured two hours after authorisation, include in your payment request:

  "amount": {
    "currency": "EUR",
    "value": 1000
  "captureDelayHours": 2,

Capture a payment

To manually capture a payment:

  1. From the payment response or the AUTHORISATION webhook, get the pspReference of the authorisation you want to capture.
  2. Make a POST request to the /payments/paymentPspReference/captures endpoint, where paymentPspReference is the pspReference of the authorisation you want to capture.
    In your request, include:
    Parameter Required Description
    merchantAccount -white_check_mark- The name of your merchant account that is used to process the payment.
    amount.value -white_check_mark- The amount in minor units (without a decimal point) being captured. This must be the same as or, in case of a partial capture, less than the authorised amount.
    amount.currency -white_check_mark- This must match the currency of the payment you're capturing.
    reference Your unique identifier for the capture operation. The reference field is useful to tag a partial capture for future reconciliation.
    The next example shows how to capture a 25.00 EUR payment authorisation that has the pspReference WNS7WQ756L2GWR82.
    curl \
    -H 'x-api-key: YOUR_API_KEY' \
    -H 'content-type: application/json' \
    -d '{
    String xApiKey = "YOUR_X-API-KEY";
    Client client = new Client(xApiKey,Environment.TEST);
    Checkout checkout = new Checkout(client);
    var paymentCaptureRequest = new CreatePaymentCaptureRequest();
    var amount = new Amount();
    String paymentPspReference = "WNS7WQ756L2GWR82";
    var response = checkout.paymentsCaptures(paymentPspReference, paymentCaptureRequest);
  3. In the capture response, note the following:
    • paymentPspReference: the PSP reference of the authorisation.
    • pspReference: the PSP reference associated with this capture request. This is different from the PSP reference of the authorisation.
    • status: received. Your capture request will be processed asynchronously. You will receive the result in a webhook.
    /captures response
      "merchantAccount": "YOUR_MERCHANT_ACCOUNT",
      "paymentPspReference": "WNS7WQ756L2GWR82",
      "pspReference": "JDD6LKT8MBLZNN84",
      "reference": "YOUR_UNIQUE_REFERENCE",
      "status": "received",
      "amount": {
        "currency": "EUR",
        "value": 2500
  4. Wait for the CAPTURE notification webhook to learn the outcome of the request.

CAPTURE webhook

When we have processed your capture request, we send you a notification webhook with:

  • eventCode: CAPTURE.
  • originalReference: the PSP reference of the authorisation.
  • pspReference: the PSP reference associated with the capture request.
  • success: indicates whether the capture request was successful. Possible values:
    • true: the capture request is valid (for example, the authorisation has not expired, and the balance is available) and has been submitted to the bank/third-party processor. In most cases, this means that the funds will be transferred to your account. For information on why the card scheme can still reject the capture, refer to Failed capture.
    • false: the capture request failed. The notification includes a reason field with a short description of the problem. Review the reason, fix the issue if possible, and resubmit the capture request.

For more information about the included fields, see the CAPTURE notification reference.

Partial capture

With some payment methods, you can also partially capture a payment. For partial captures, your account can be set to perform either:

In both cases, to partially capture a payment:

  • Make a call to the /payments/paymentPspReference/captures endpoint specifying:
    • amount.value: the partial amount that you want to capture. This amount must be smaller than the original authorised amount.

Single partial capture

For single partial captures, any unclaimed amount that is left over after partially capturing a payment is automatically cancelled.

For some schemes, you can flag each payment request as either a pre-authorisation or a final authorisation. For partial captures, we recommend that you flag the payment request as a pre-authorisation. For more information, refer to Card authorisation types.

Multiple partial captures

When your account is enabled for multiple partial captures, the unclaimed amount after an initial capture is not automatically cancelled.
This is necessary for some businesses models such as an ecommerce site where capture takes place upon shipment, or in Unified Commerce scenarios where the shopper orders items in a physical store. If you have an order with multiple items to ship, each shipment would correlate to a partial capture.
To enable multiple partial captures, contact our Support Team.


In rare cases, a capture fails even after you received a CAPTURE notification with successtrue. The successful notification means that we sent the request to the card scheme, but the scheme can still reject the request at this point. This can even happen a few days after you submitted the capture request.
Most of the time Adyen can fix the issue, so that you will eventually receive the funds. Sometimes, however, you need to take action yourself. To learn why a capture can fail and what, if anything, you need to do in each case, refer to Reasons for failed capture.
When a capture fails, we inform you of this with a notification containing:

  • eventCode: CAPTURE_FAILED
  • originalReference: the pspReference of the authorisation.
  • pspReference: the pspReference of the capture request.

The notification contains the reason why the card scheme rejected the capture. You can also find the capture failure reason on the Payment details page in your Customer Area.

CAPTURE_FAILED notification
             "reason":"Capture Failed",

An overview of failed captures is available in your Payment accounting report.

Testing failed captures

In our test environment, you can check how your integration handles failed captures:

  1. Make a card payment, specifying:

    • holderName: capture failed
      "amount": {
        "currency": "EUR",
        "value": 500
      "reference": "Capture failed test",
      "paymentMethod": {
        "type": "scheme",
        "encryptedCardNumber": "test_4111111111111111",
        "encryptedExpiryMonth": "test_03",
        "encryptedExpiryYear": "test_2030",
        "encryptedSecurityCode": "test_737",
        "holderName": "capture failed"
      "returnUrl": "",
      "merchantAccount": "YOUR_MERCHANT_ACCOUNT"
  2. Capture this payment, using either automatic or manual capture.

Once we have processed the capture request, we send you a CAPTURE_FAILED notification.

This request may take several hours to process.

See also