---
title: "Create capture"
method: POST
path: "/payments/{paymentId}/captures"
tags: ["Captures API"]
---

# Create capture

`POST /payments/{paymentId}/captures`

Capture an *authorized* payment.

Some payment methods allow you to first collect a customer's authorization, and capture the amount at a later point.

By default, Mollie captures payments automatically. If however you configured your payment with `captureMode: manual`, you can capture the payment using this endpoint after having collected the customer's authorization.

> 🔑 Access with
>
> [API key](/reference/authentication)
>
> [Advanced access token with **payments.write**](/reference/authentication)
>
> [OAuth access with **payments.write**](/reference/authentication)

## Request body

- object
  - `resource` string — Indicates the response contains a capture object. Will always contain the string `capture` for this endpoint.
  - `id` string — The identifier uniquely referring to this capture. Example: `cpt_mNepDkEtco6ah3QNPUGYH`.
  - `mode` string — Whether this entity was created in live mode or in test mode. Possible values: `live` `test`
  - `description` string — The description of the capture.
  - `amount` object, nullable — The amount captured. If no amount is provided, the full authorized amount is captured.
    - `currency` string, required — A three-character ISO 4217 currency code.
    - `value` string, required — A string containing an exact monetary amount in the given currency.
  - `settlementAmount` object, nullable — In v2 endpoints, monetary amounts are represented as objects with a `currency` and `value` field.
    - `currency` string, required — A three-character ISO 4217 currency code.
    - `value` string, required — A string containing an exact monetary amount in the given currency.
  - `status` string — The capture's status. Possible values: `pending` `succeeded` `failed`
  - `metadata` union — Provide any data you like, for example a string or a JSON object. We will save the data alongside the entity. Whenever you fetch the entity with our API, we will also include the metadata. You can use up to approximately 1kB.
    - string
    - number
    - object
    - string[]
  - `paymentId` string — The unique identifier of the payment this capture was created for. For example: `tr_5B8cwPMGnU6qLbRvo7qEZo`. The full payment object can be retrieved via the payment URL in the `_links` object.
  - `shipmentId` string, nullable — The unique identifier of the shipment that triggered the creation of this capture, if applicable. For example: `shp_gNapNy9qQTUFZYnCrCF7J`.
  - `settlementId` string, nullable — The identifier referring to the settlement this capture was settled with. For example, `stl_BkEjN2eBb`. This field is omitted if the capture is not settled (yet).
  - `createdAt` string — The entity's date and time of creation, in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format.
  - `_links` object — An object with several relevant URLs. Every URL object will contain an `href` and a `type` field.
    - `self` object, required — In v2 endpoints, URLs are commonly represented as objects with an `href` and `type` field.
      - `href` string, required — The actual URL string.
      - `type` string, required — The content type of the page or endpoint the URL points to.
    - `payment` object, required — The API resource URL of the [payment](get-payment) that this capture belongs to.
      - `href` string, required — The actual URL string.
      - `type` string, required — The content type of the page or endpoint the URL points to.
    - `settlement` object, nullable — The API resource URL of the [settlement](get-settlement) this capture has been settled with. Not present if not yet settled.
      - `href` string — The actual URL string.
      - `type` string — The content type of the page or endpoint the URL points to.
    - `shipment` object, nullable — The API resource URL of the [shipment](get-shipment) this capture is associated with. Not present if it isn't associated with a shipment.
      - `href` string — The actual URL string.
      - `type` string — The content type of the page or endpoint the URL points to.
    - `documentation` object, required — In v2 endpoints, URLs are commonly represented as objects with an `href` and `type` field.
      - `href` string, required — The actual URL string.
      - `type` string, required — The content type of the page or endpoint the URL points to.

## Response `201`

The newly created capture object. For a complete reference of the capture object, refer to the [Get capture endpoint](get-capture) documentation.

## Other responses

- `404` — No entity with this ID exists.
- `422` — The request contains issues. For example, if the capture amount is missing.
- `429` — Rate Limit has been reached.

---

[API](https://skmtc.net/mollie/apis/accepting-payments.md) · [All operations](https://skmtc.net/mollie/apis/accepting-payments/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mollie/accepting-payments/versions/4b45df3039ef/schema)