# Captures a Single Auth, Frequent and Frequent Auth

Endpoint: POST /capture/{id}
Version: 2.0
Security: accountId, apiKey

## Path parameters:

  - `id` (string, required)
    Resource Identification

## Request fields (application/json):

  - `transaction_key` (string)
    Your internal key identifying this capture
    Example: "key example"

  - `capture_date` (string)
    The date when the action should be executed. This field specifies the exact day for capturing the transaction, formatted as "YYYY-MM-DD" (e.g., "2024-06-30"). It is optional and defaults to the current date if not specified.
    Example: "2022-11-11"

  - `account` (object)
    For multi-account clients.

  - `account.id` (string)
    The uuid of the account.

  - `splits` (array)
    Used in split payments.

  - `splits.split_key` (string)
    The merchant's internal key for identifying the split.
    Example: "example key"

  - `splits.split_descriptive` (string)
    The description of the split.

  - `splits.value` (number, required)
    The split funds, rounded to 2 decimals.
    Example: 10.56

  - `splits.account` (object)
    The account owner of the split.

  - `splits.margin_value` (number)
    The margin funds, rounded to 2 decimals.

  - `splits.margin_account` (object)
    The account used for the margin.

  - `force_3ds` (boolean)
    Whether or not you want to force the 3DS authentication on Credit Cards (used only on Frequent capture without authorisation).

  - `descriptive` (string)
    This will appear in the bank statement/mbway application.
    Example: "descriptive example"

  - `value` (number)
    Value will be rounded to 2 decimals.
    Example: 20.55

  - `mbway_sdk` (object)

  - `mbway_sdk.purchase_token` (string)

  - `mbway_sdk.initial_timestamp` (string)

  - `mbway_sdk.merchant_operation_id` (string)
    unique-concatenation between client identifier and client operation id (total max 20 chars)

  - `mbway_sdk.payload` (string)

## Response 201 fields (application/json):

  - `status` (string)
    Example: "ok"

  - `message` (array)
    Example: ["Your request was successfully created"]

  - `id` (string)
    A unique identifier for the resource. While typically formatted as a UUID (Universally Unique Identifier), it can also be in other formats as defined by the user. This field ensures the resource can be distinctly recognized and referenced.
    Example: "677dbec9-ec19-4a78-9e08-3d2901c7a32b"

## Response 400 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 403 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 404 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 412 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 422 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 428 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 429 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.

## Response 500 fields (application/json):

  - `status` (string, required)

  - `message` (array, required)
    An array of human-readable messages included in the response. These messages provide detailed information about the success of the operation or explain the reasons for any failure. This field is always present in the response to ensure clarity and transparency regarding the outcome of the API request.