Capture Payment

Use this endpoint to capture funds from a previously authorized payment. During an authorization flow, the payment gateway verifies the payment method and reserves funds on the shopper's account — but does not transfer them. Capturing completes the transaction by collecting those reserved funds.

You can capture payments for payment methods that follow an authorization flow (for example, Card and selected alternative payment methods). Availability and behavior depend on the configured acquirer and product setup.

Capture behavior follows product guidelines and the capabilities of the underlying acquirer.


When to Capture

Capture is required when a payment was created with:

{
  "immediateCapture": false
}

In this case:

  1. The payment is authorized
  2. Funds are reserved on the shopper’s account
  3. You must call the capture endpoint to collect the funds

If immediateCapture was set to true, no separate capture call is required.


Partial Manual Capture

Partial capture allows you to capture only part of the authorized amount.

The behavior depends on whether you perform a single partial capture or multiple partial captures.


Capture Types

Type of Partial CaptureDescription
Single partial captureAny remaining authorized amount that is not captured is automatically cancelled.
Multiple partial capturesThe remaining authorized amount is not automatically cancelled and can be captured later in additional capture requests.

Single Partial Capture

When performing a single partial capture:

  • You capture part of the authorized amount.
  • The remaining unclaimed amount is automatically cancelled.
  • The payment is considered fully processed after the capture.

This approach is typically used when:

  • The final amount is known at the time of capture.
  • Only one shipment or delivery occurs.

Multiple Partial Captures

When performing multiple partial captures:

  • The remaining authorized amount stays open after the first capture.
  • You may submit additional capture requests until the full authorized amount is captured.
  • The payment transitions to captured once the total captured amount equals the authorized amount.

This is commonly used in business models such as:

  • Ecommerce shipments fulfilled in multiple batches
  • Omnichannel scenarios (store pickup + warehouse shipment)
  • Orders with items delivered separately

Availability of partial capture behavior depends on the underlying acquirer and card scheme rules.


Endpoint

POST /v1/{pspReference}/capture
  • pspReference is the unique identifier returned when the payment session was created.
  • The idempotency-key header is mandatory.

Full Capture

To capture the full remaining authorized amount, send the request without a body or leave the amountDetailsempty.

{
  "reference": "Optional, for example: Goods delivered - partial shipment"
}

Example

POST /v1/{pspReference}/capture

Partial Capture

To capture a partial amount, include an amountDetails object in the request body.

Example

{
  "merchantId": "Aera Merchant ID",
  "amountDetails": {
    "amount": 5000,
    "currency": "NOK"
  },
  "reference": "Optional, for example: Goods delivered - partial shipment",
  "cancelRemainingReservation": true
}
  • cancelRemainingReservation: If true, any remaining authorized amount is cancelled after this capture. Set this for the final partial capture.

Field Reference

Path Parameter

FieldTypeRequiredDescription
pspReferencestring (UUID v7)YesUnique payment identifier returned when the checkout session was created.

Request Headers

FieldTypeRequiredDescription
x-api-keystringYesAPI key assigned by Aera.
merchant-idstringYesMerchant ID assigned by Aera.
idempotency-keystring (UUID v7)YesUnique identifier for this capture request. Required for safe retries.
AuthorizationstringYesBearer <access token>
AcceptstringYesapplication/vnd.payments.v1+json
Content-TypestringYesapplication/vnd.payments.v1+json

Request Body

FieldTypeRequiredDescription
merchantIdstringYes (for partial capture)Merchant ID assigned by Aera.
amountDetailsobjectNoRequired for partial capture. If omitted, the full remaining authorized amount is captured.
referencestringNoOptional free-text reference for the operation

amountDetails

FieldTypeRequiredDescription
amountintegerYes (for partial capture)Amount to capture in minor units.
currencystring (ISO 4217)Yes (for partial capture)Currency code (e.g., NOK).

Response

FieldTypeRequiredDescription
responseInfoobjectYesHigh-level processing result information.
operationInfoobjectYesInformation about the capture operation result.

responseInfo

FieldTypeRequiredDescription
responseCodestring (3 digits)YesResponse code from a predefined list.
responseTextstringYesHuman-readable description of the result.

operationInfo

FieldTypeRequiredDescription
typestringYesOperation type (CAPTURE).
statusstringYesOperation status (e.g., SUCCESS, FAILED).
capturedAmountobjectYesAmount successfully captured.

capturedAmount

FieldTypeRequiredDescription
amountintegerYesCaptured amount in minor units.
currencystring (ISO 4217)YesCurrency code.

What’s Next

Did this page help you?