Request a settlement advance
Submit the Permit2 signature generated from the presign endpoint along with the witness payload. Funding runs asynchronously after this call returns.
Idempotent on tradeId: replays for the same trade either return the
in-progress settlement advance or short-circuit when the trade already
has a non-failed active settlement advance.
Calling /reserve first is optional. The request body is the same
whether or not a prior reservation exists.
Collateral rounding: when the repayment is complete and collateral is released, Circle rounds the collateral amount to 2 decimal places.
Authorizations
Body
Request body for accepting a settlement advance by submitting a Permit2 signature.
Universally unique identifier (UUID v4) idempotency key. This key is utilized to ensure exactly-once execution of mutating requests. To create a UUIDv4 go to uuidgenerator.net. If the same key is reused, it will be treated as the same request and the original response will be returned.
"a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11"
Response
Settlement advance requested; funding in progress.
Settlement advance accepted; funding in progress.
Lifecycle status of the credit advanced against a settlement.
funds_reserved-- credit reserved on the line, awaiting maker action.requested-- maker submitted the request; Circle is moving funds.disbursed-- funds delivered to the funder passthrough wallet.past_due-- repayment window has elapsed without full repayment.paid-- credit fully repaid.rejected-- credit line rejected the advance request.expired-- reservation expired before being consumed.canceled-- maker or Circle canceled the advance.failed-- Circle could not deliver the advance onchain before the trade matured. No credit was extended and the reserved credit is released.
funds_reserved, requested, disbursed, past_due, paid, rejected, expired, canceled, failed "disbursed"