# Incremental auth

Incremental authorization operation creates additional authorization transactions on top of an estimated authorization to increase the total authorized amount for the order.


  The payment configuration conditions must be met.


                
    Maximum 50 increments allowed per order.


This operation creates a auth transaction with authorization_type incremental within the same order.

Endpoint: POST /increment
Version: 1.0.0
Security: MerchantID

## Header parameters:

  - `merchant` (string, required)
    Unique public key provided upon registration and must be shared for identification purposes.
    Example: "api_pk_7b197...ba108f842"

  - `signature` (string, required)
    Request signature that allows verification of merchant authenticity on the payment gateway server.
    Example: "M2E3OTkyNzcz...xMmExODI4"

## Request fields (application/json):

  - `order_id` (string, required)
    Unique order identifier defined by the merchant, which can be used to find the payment.

  - `amount` (integer, required)
    Increment amount in the smallest currency unit.

                
  For instance, 1020 means 10 EUR and 20 cents.
  The amount represents the increment value to add to the initial authorization, not the total amount.

## Response 200 fields (application/json):

  - `body` (object) — one of:
    - Success:
      - `transaction` (object)
        Transaction details for the incremental authorization.
      - `transaction.id` (string)
        Unique transaction identifier.
        Example: "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
      - `transaction.amount` (integer)
        Increment amount from the request in the smallest currency unit.
        Example: 500
      - `transaction.currency` (string)
        Currency code from the initial order.
        Example: "EUR"
      - `transaction.status` (string)
        Status of the transaction.
        Example: "processing"
    - Authentication failed:
      - `error` (object, required)
        Error object.
      - `error.code` (string, required)
        Unauthorized access due to invalid credentials.
        Example: "1.01"
      - `error.messages` (array, required)
        Array of error messages applied to the decline payment.
        Example: ["Authentication failed"]
    - Error:
      - `error` (object, required) — one of (discriminator: code):
        Error object.
        - 2.01 Invalid data:
          - `messages` (array, required)
            Array containing messages that specify why the payment was declined due to validation errors.


  These messages can range from an incorrect card number to an invalid security code or billing address.
            Example: ["Invalid data"]
        - 2.01 Order not found:
          - `messages` (object, required)
            Object containing key-value pairs that clarify the reason for the payment decline, particularly in cases where the requested order does not exist.
        - 2.04 Card brand is not supported:
          - `messages` (array, required)
            Array containing messages that specify why the payment was declined due to unsupported card brand for incremental authorization.


  Supported card brands include American Express (Amex), Cartes Bancaires, Diners, Discover, JCB, Mastercard, Mexico Domestic (Network MX) and Visa.
            Example: ["Card brand is not supported"]
        - X.XX:
          - `messages` (array, required)
            Array containing either strings or objects that provide details about the error or status.


  When it is an array of strings, each string describes a separate issue. When it is an object, the object will contain key-value pairs explaining the issue in more detail.
          - `recommended_message_for_user` (string)
            Message with recommended next steps or additional information.
            Example: "The user’s card balance has insufficient funds."
      - `error.code` (string)
        Gateway error code for the declined payment.