Skip to main content
POST
Increment Authorization
This request raises the amount of a previously authorized payment (an incremental authorization). It is designed for open-ended-amount scenarios — EV charging, fuel, hospitality, car rental — where you authorize a small amount first and grow the hold as the final amount becomes known, then capture once with the capture API. The amount you send is a delta: how much to add to the current authorized amount. Yuno translates it to each provider’s expected semantics. Each increment creates its own AUTHORIZE_INCREMENT transaction with a per-increment result, visible in Retrieve Payment. Increments are notified with the payment.authorize webhook event, so subscribe to the AUTHORIZE trigger to receive them; there is no separate increment event. A successful increment raises payment.amount.authorized; payment.amount.value keeps the original amount. A declined increment leaves the previously authorized amount untouched. Multiple increments can be performed on the same authorization, but they must be sequential: a new increment requested while a previous one is still in progress returns a 400. Note that this request requires an X-Idempotency-Key. Check the Authentication page for more information.

Capturing after increments

A capture with an explicit amount can settle any amount up to the current total authorized (original authorization plus all succeeded increments). A capture without an amount settles the transaction’s full current hold — the original authorized amount plus all SUCCEEDED increments on that transaction. Increments still PENDING at capture time are not included.
The original authorization must opt inSome providers only allow increments on authorizations created as pre-authorization holds. Set authorization_type: "PRE_AUTHORIZATION" (together with capture: false) when creating the payment; see the Cancel and Capture Flow guide. When the provider rejects the increment — because the original authorization was not a pre-authorization, or because the provider’s increment limits were exceeded (for example more than 10 increments, or a total above 5× the initial amount) — the increment transaction is returned with the AUTHORIZATION_NOT_INCREMENTABLE response code.

Provider support

Support is provider-dependent. If the provider routed for the payment does not support incremental authorizations, the call still returns 201, but with an increment transaction whose status is ERROR and whose response_code is OPERATION_NOT_SUPPORTED_BY_PROVIDER — it is not an HTTP error, so branch on the transaction status, not the HTTP status code. The previously authorized amount is left untouched. Revolut is currently the only provider with incremental authorization support. Other providers (Stripe, Adyen, Checkout.com, CyberSource) are on the roadmap and not yet available; calling the endpoint on them today returns the OPERATION_NOT_SUPPORTED_BY_PROVIDER transaction described above.

Authorizations

public-api-key
string
header
default:<Your public-api-key>
required
private-secret-key
string
header
default:<Your private-secret-key>
required
X-Idempotency-Key
string
header
default:<Your X-Idempotency-Key>
required

Path Parameters

payment_id
string
required

The unique identifier of the payment (UUID, 36 chars).

transaction_id
string
required

The unique identifier of the original AUTHORIZE transaction to increment (UUID, 36 chars).

Body

application/json
amount
object
required

The amount to ADD to the current authorized amount (a delta, not the new total). The currency must match the original authorization.

merchant_reference
string
required

The reference for this increment.

description
string

Optional description of the increment.

Response

201

id
string

Unique identifier of the increment transaction (UUID).

type
string

Transaction type.

Example:

"AUTHORIZE_INCREMENT"

status
enum<string>

Per-increment result. SUCCEEDED: the hold was raised. DECLINED: the issuer or provider declined this increment; the previous authorized amount stands. PENDING: the provider processes increments asynchronously; the final result is delivered via webhook. ERROR: the increment could not be processed.

Available options:
SUCCEEDED,
DECLINED,
PENDING,
ERROR
amount
object

The delta added by this increment.

merchant_reference
string

The reference sent in the request.

parent_transaction_id
string

The transaction_id of the original AUTHORIZE transaction this increment belongs to.

response_code
string

Yuno response code for this increment: the transaction sub-status when the provider returns one, otherwise the transaction status (for example SUCCEEDED, PENDING_PROVIDER_CONFIRMATION, AUTHORIZATION_NOT_INCREMENTABLE). It is not an ISO 8583 issuer code. AUTHORIZATION_NOT_INCREMENTABLE indicates the provider rejected the increment — either the original authorization was not created as PRE_AUTHORIZATION, or the provider's increment limits were exceeded (for example more than 10 increments, or a total above 5× the initial amount on Revolut).

response_message
string

Human-readable detail of the result.

provider_data
object

Raw provider identifiers and status for this increment.

payment
object

The parent payment after this increment.