Skip to main content
This group covers the end of an escrow: the buyer releasing funds on delivery, either party raising a dispute, and you (the merchant) resolving it. It also includes the merchant-wide read feeds. See Escrow lifecycle for the states involved.
Watch the customer-id header carefully here:

Release & dispute (per-customer)

RouteMethod & pathWhat it does
Buyer confirm paymentPOST /v1/escrow/confirm-payment/{escrowId}Buyer confirms delivery on a standard escrow; releases the full amount and closes it COMPLETED. customer-id = buyer.
Submit disputePOST /v1/escrow/submit-dispute/{paymentToken}Open or reply to a dispute (escrow must be OPENED). multipart/form-data with a message and optional evidence file. Only the buyer can open a dispute; the seller can only respond once one is raised. Milestone escrows can’t be disputed. customer-id required.
List my disputesGET /v1/escrow/dispute/getA customer’s disputes, with optional paymentToken / date filters. customer-id required.
Get dispute by escrow IDGET /v1/escrow/dispute/get/{escrowId}The dispute thread for one escrow. customer-id required.

Merchant-wide (no customer-id)

RouteMethod & pathWhat it does
List all customers’ disputesGET /v1/escrow/all-disputeEvery dispute across all your customers, paginated.
Get escrow feedsGET /v1/escrow/feedsAll customers’ escrows, with status / customerId / categoryId / date filters.
Resolve disputePOST /v1/escrow/dispute/resolve/{escrowId}You settle the dispute. multipart/form-data: resolution text + status (COMPLETED releases to seller, REFUNDED returns to buyer) + optional file.

Resolution paths

1

Happy path

Buyer confirmsCOMPLETED.
2

Contested

The buyer opens a dispute (DISPUTED); the seller responds (INVESTIGATING). Standard escrows only.
3

Merchant decides

You resolveCOMPLETED (seller paid) or REFUNDED (buyer refunded).