Reconcile payouts
Run a periodic job so your records match every transfer, even when webhooks are missed.
Payout webhooks notify; GET /v1/payouts/{payoutId} is the source of truth. A misconfigured or disabled endpoint drops events without telling you, so run a periodic job over the payouts your records show as not final:
-
List payouts that aren't final. Call
GET /v1/payouts?status=requires_action&status=processing, followingnextCursoruntil it isnull.curl "https://api.merchant.pay.walletconnect.com/v1/payouts?status=requires_action&status=processing" \ -H "Api-Key: YOUR_PAYOUT_API_KEY" -
Update your records. For each payout your records show as not final, call
GET /v1/payouts/{payoutId}and apply the result if itspayoutStateVersionis higher than yours. -
Fund what is waiting. Compare each balance's
shortfallinGET /v1/payout-accountswith what you have already sent. See Balances.
List filters
GET /v1/payouts accepts these query parameters:
| Parameter | Meaning |
|---|---|
status | Repeat for several: ?status=processing&status=succeeded. |
referenceId | Payouts with this reference. |
startTs, endTs | Created at or after startTs, and before endTs (RFC 3339). |
limit | 50 by default, 200 at most. |
cursor | nextCursor from the previous page. |
Results are newest first, in data.