Takes a kind 9735 receipt directly or fetches it from relays by event id, then r
Takes a kind 9735 receipt directly or fetches it from relays by event id, then runs eight named checks and reports each one separately with its reason. The receipt signature and the signature of the zap request enclosed in the description tag are verified per BIP-340. The invoice is decoded and its amount is compared against the amount tag of the zap request, since those two can disagree and only the invoice was payable.
Answeringour last check, 2026-10-10
1 of 1checks answered this week
952 msmedian answer time
$0.002listed price per call
$0.002price it asked us
Paid test badge: not yet. The checks above are free: we call the tool without paying and read the payment request it sends back. The Verified badge needs paid calls whose answers match the promised output, and nobody can buy a badge.
Endpoint
POST https://nostr.halowerk.com/zap-receipt-check
| Category | Everything else |
|---|---|
| Provider host | nostr.halowerk.com |
| Networks | eip155:8453 |
| Payment schemes | exact |
| Self-reported calls, 30 days | 2 from 2 payers (the provider's figure, not ours) |
Our checks, last 30 days
| Day | Result | HTTP | Asked | Time |
|---|---|---|---|---|
| 2026-10-10 | valid payment request | 402 | $0.002 | 952 ms |
Example input (from the provider)
{
"body": {
"event_id": "beispiel",
"receipt": {}
},
"bodyType": "json",
"method": "POST",
"type": "http"
}
Promised output schema (from the provider)
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"input": {
"additionalProperties": false,
"properties": {
"body": {
"additionalProperties": false,
"properties": {
"event_id": {
"description": "Event id of the receipt as hex, note or nevent. Fetched from the relays when receipt is not given.",
"type": "string"
},
"receipt": {
"description": "The complete kind 9735 event. Either this or event_id is required.",
"type": "object"
},
"recipient_lightning_address": {
"description": "Lightning address of the recipient, for example name@domain. Given, the issuer is compared against the nostrPubkey published there.",
"type": "string"
},
"relays": {
"description": "wss relay addresses used when fetching by event_id.",
"items": {
"type": "string"
},
"maxItems": 12,
"type": "array"
}
},
"type": "object"
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
},
"method": {
"enum": [
"POST",
"PUT",
"PATCH"
],
"type": "string"
},
"type": {
"const": "http",
"type": "string"
}
},
"required": [
"type",
"method",
"bodyType",
"body"
],
"type": "object"
}
},
"required": [
"input"
],
"type": "object"
}