Payer routes

Report the deposit

POST/v1/payer/deposit-requests/{id}/relay/quotes/{rli}/sent

The wallet sent the quote's deposit; Payday follows it from here.

Unauthenticated · Payday-Payer-Session unlocks gated content.

Request

Shell
curl -fsS -X POST "$API/v1/payer/deposit-requests/dr_0198f80c-…/relay/quotes/rli_0198f80c-…/sent" \
  -H "Content-Type: application/json" \
  -d '{ "transaction_hash": "0x…" }'

Response

200 OK
{ "…": "the payer view", "relay": { "id": "rli_0198f80c-…", "status": "sent", "origin_chain_id": "8453", "origin_transaction_hash": "0x…", "fill_transaction_hash": null, "created_at": "2026-09-06T12:06:00Z" } }

Once. From then on the indexer asks Relay what became of the request, attributes the delivered USDC to the attested wallet when Relay names it as the depositor, and the payer view's relay block shows where it stands. The hash is advisory; the origin transaction Relay records is what the proof names.

Headers

Payday-Payer-Sessionstring
Required for gated modes.

Path parameters

iddr_ idrequired
rlirli_ idrequired
The quote.

Body

transaction_hashstringrequired
The deposit step's transaction, 0x hex, 32 bytes.

Response

Payer view, with relay.status sent.

Status codes

  • 404relay_intent_not_found Not this request's quote.
  • 409relay_intent_not_quoted Already reported, or expired unsent.
  • 409relay_transaction_claimed That hash already pays another quote.
  • 410deposit_request_not_payable