Increment Authorization
Raises an existing authorization hold by a delta amount, without creating a new authorization.
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 explicitamount 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.
Provider support
Support is provider-dependent. If the provider routed for the payment does not support incremental authorizations, the call still returns201, 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.
OPERATION_NOT_SUPPORTED_BY_PROVIDER transaction described above.Authorizations
Path Parameters
Body
Response
201
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.
SUCCEEDED, DECLINED, PENDING, ERROR 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).