> **Can't find what you're looking for?** Use `search_docs` on the docs MCP server at `https://mpp.dev/api/mcp` to find what you need.

# 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.

:::info
The `Payment-Receipt` header is optional. Servers typically include it for auditability, but clients don't need it for correct operation.
:::

## Header

```http
HTTP/1.1 200 OK
Payment-Receipt: eyJtZXRob2QiOiJ0ZW1wbyIsInJlZmVyZW5jZSI6IjB4Nzg5YWJjLi4uIiwic3RhdHVzIjoic3VjY2VzcyIsInRpbWVzdGFtcCI6IjIwMjUtMDEtMTVUMTI6MDA6MDBaIn0
Content-Type: application/json

{ "data": "Payment received." }
```

The Receipt is a base64url-encoded JSON object.

## Structure

```json
{
  "method": "tempo",
  "reference": "0x789abc...",
  "status": "success",
  "timestamp": "2025-01-15T12:00:00Z"
}
```

### Fields

| Field | Description |
|-------|-------------|
| `externalId` | Optional external reference echoed from the Credential payload |
| `method` | Payment method used |
| `reference` | Method-specific payment reference (for example, transaction hash or invoice ID) |
| `status` | Payment outcome (`success`) |
| `subscriptionId` | Optional server-issued subscription identifier |
| `timestamp` | When the payment was processed |

Payment method specifications can define additional fields.

## 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](https://paymentauth.org) — Read the full specification