Receipts

Server acknowledgment of successful payment

A Receipt is the server's acknowledgment of successful payment. Return Receipts in the Payment-Receipt header on successful responses.

HTTP/1.1 200 OK
Payment-Receipt: eyJzdGF0dXMiOiJzdWNjZXNzIiwibWV0aG9kIjoidGVtcG8iLCJ0aW1lc3RhbXAiOiIyMDI1LTAxLTE1VDEyOjAwOjAwWiJ9
Content-Type: application/json
 
{ "data": "Payment received." }

The Receipt is a base64url-encoded JSON object.

Structure

{
  "challengeId": "qB3wErTyU7iOpAsD9fGhJk",
  "method": "tempo",
  "reference": "0xtx789abc...",
  "settlement": {
    "amount": "1000",
    "currency": "usd"
  },
  "status": "success",
  "timestamp": "2025-01-15T12:00:00Z"
}

Fields

Field	Description
`challengeId`	The Challenge this Receipt responds to
`method`	Payment method used
`reference`	Method-specific payment reference (for example, transaction hash or invoice ID)
`settlement`	Actual amount and currency settled
`status`	Payment outcome (`success`)
`timestamp`	When the payment was processed

Use cases

Receipts enable:

Auditing—Clients can log payment confirmations
Dispute resolution—Reference IDs link to payment network records
Reconciliation—Match payments to requests

Payment method references

Settlement type	Reference format
On-chain transfer	Transaction hash (`0xtx789...`)
Card authorization	Authorization reference (`auth_1234...`)
Invoice payment	Invoice ID (`inv_1234...`)

Learn more

IETF Specification

Read the full specification

Suggest changes to this page