# X Pay Payment Receipt

> X Pay Payment Receipt is a paid API for AI agents from www.api-xpay.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Returns a payment receipt with full transaction details for an x402 USDC payment made on Base network

## Facts

- Endpoint: GET https://www.api-xpay.com/x402/payment
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x-pay-payment-receipt-046d5f0f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OKsz90aPgcBWZtK-KX5_q

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability x-pay-payment-receipt-046d5f0f
```

Example prompt: Can you pull up the payment receipt from X Pay for that recent USDC micropayment on Base — I want to see the transaction hash, payer address, and whether it was successful?

## When to prefer this

Use this endpoint when you need to retrieve or verify the details of an x402 USDC micropayment processed through X Pay on Base network — particularly for audit trails, payment confirmation before fulfilling a service, or reconciling transaction records. Prefer this over generic blockchain explorers when you need structured payment metadata tied to a specific API request ID.

## Known failure modes

- Payment not yet confirmed on-chain — returns success: false or empty transaction hash
- Invalid or missing x402 payment header — returns 402 or authentication error
- Network congestion causing delayed transaction confirmation
- Wrong HTTP method supplied — endpoint only accepts GET, HEAD, or DELETE
- Transaction hash unavailable if payment is still pending

## How this service works

Pay-per-request utility APIs powered by x402 using USDC on Base.

## Output

Returns a JSON object with a 'payment' object containing: payer wallet address, receiver wallet address, USDC amount, network (Base), request ID, and transaction hash — plus a 'success' boolean and 'service' name confirming the payment was processed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "headers": {
     "type": "object",
     "additionalProperties": {
      "type": "string"
     }
    },
    "queryParams": {
     "type": "object",
     "additionalProperties": {
      "type": "string"
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "payment": {
   "asset": "USDC",
   "payer": "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb0",
   "amount": "0.001",
   "network": "base",
   "receiver": "0x589a2314a2E05F45e40C4823Da3Ba58D421dB3d8",
   "requestId": "req_abc123",
   "transactionHash": "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef"
  },
  "service": "X Pay",
  "success": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x-pay-payment-receipt-046d5f0f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.api-xpay.com](https://www.zero.xyz/host/www.api-xpay.com/llms.txt)