Issuer contract

Issuer-side recovery

What issuers must store and expose so a buyer can redownload a paid HTTP body after settlement without a second charge. This is not a Sluzen buyer API. Sluzen proves payment; the issuer owns long-lived delivery of the resource bytes.

Does not change the 402 wire, proxy cache, facilitator settle, or GET /admin/calls. Durable buyer retrieve on Sluzen remains deferred.

HTTP 402 guide →

Sluzen today

What Sluzen already does

After settlement_ok, the buyer confirms settle with verifyBuyerPayment / explorer / proof and the txHash (often on 409 replay). Default proxy may redeliver from a same-process TTL cache (~15 minutes) on the same PAYMENT-SIGNATURE; after TTL or restart → 409 + txHash when known — payment proof, not a download. Facilitator: Sluzen never stored the handler body; same-process facilitatorSettle may return a cached handler result on 409 + txHash.

callId / txHash reconcile payment. They do not redownload a lost body from Sluzen. GET /admin/calls is issuer-scoped only.

Per paid attempt

Must store

Persist at least: callId, txHash when known, exact body bytes, HTTP status, Content-Type, resource key (proxy sourceRoute or facilitator URL), and stored-at for TTL. Same semantics for XRP, allowlisted RLUSD, and Base USDC.

On the issuer host

Must expose

Document and implement recovery on the issuer’s stack: authenticate the buyer (payment proof / txHash + callId, receipt, secret, or session); on success return the same stored body with no second ledger settle and no fresh PAYMENT-REQUIRED for that purchase. Publish URL shape, auth rules, and retention TTL in the issuer’s own docs.

Recommended outcomes: 200 within TTL; 401/403 auth fail; 404 unknown or expired; 409 conflict without a new payable challenge.

Retention and modes

TTL, proxy, facilitator

The issuer declares retention (product SLA). Sluzen does not promise durable body retention. Proxy: origin body is forwarded once — issuer/origin must persist for durable recovery. Facilitator: body never left the issuer handler — persist there.

Replay on Sluzen (same signature after settle) is not the same as redownload on the issuer. Do not point buyers at /admin/calls as a download.

Out of scope

Non-goals

Automatic refunds or escrow; second charge for the same paid attempt; Sluzen as content store; buyers using /admin/calls; infinite body retention on Sluzen.