Skip to main content
End an hourly or recurring progressive-release contract. Closing settles what is owed before returning what is not:
  1. Approved-but-unpaid periods are released to the seller.
  2. The reservation is confirmed empty.
  3. The genuinely unused balance is refunded to the client.
  4. The escrow completes with completionSource: "progressive_close".
This is deliberately not a cancellation. A contract that ran successfully and simply has funds left over completes normally, so reporting and the client’s transaction history reflect what actually happened.
Closing is refused with 409 while any period is still pending or disputed. The response lists the blocking requestIds so you can show the client exactly what is outstanding. Resolve those periods first — a client must never be able to reclaim funds that an unresolved timesheet still has a claim on.

Path Parameters

string
required
Escrow ID

Body Parameters

string
Optional note recorded on the audit log (max 1000 characters)

Response Fields

Error Responses

409 Conflict

Periods still open
Seller not settlement-ready

400 Bad Request

Progressive release not enabled
Escrow not funded

401 Unauthorized

404 Not Found


A disputed period blocks closure until DHMAD resolves it. Resolution awards all, part, or none of the claim; any unawarded remainder returns to the escrow balance and is then included in the refund when you retry the close.
Do not use close to handle an exhausted balance. A progressive escrow with a zero balance stays open on purpose so the client can top it up with add_funds and keep the contract running.