The release_authorization operation releases previously held credits back to the usable balance, effectively canceling an existing authorization (hold).
API Behavior
- Reverses an earlier
authorizeoperation. - Moves credits from held (reserved) → usable balance.
- No consumption occurs as part of this operation.
- Always releases the entire remaining held amount; partial releases are not supported.
- Once released, the hold is considered closed.
Requirements
Requires the authorization_id of the original authorize request.
Business Use Cases
Cancellation flows When an authorized action is no longer needed.
Failure recovery Downstream processing fails after authorization.
Timeout handling Manual alternative to auto-release on hold expiry.
Usage
Ensures held credits are fully returned to the usable balance, preventing funds from remaining locked.
The response returns both the created ledger_operation object and the updated ledger_account_balance.
Sample Request
Sample Result[JSON]
URL Format
Input Parameters
Unix timestamp (in seconds) representing when the release_authorization occurred in the upstream system.
Usage
- Used for period attribution, grace-period eligibility, and reporting accuracy.
Note
Late or out-of-order submissions appear in arrival order, while attribution and eligibility logic rely on ledger_operation_timestamp.