Authentication
This endpoint is public. It takes no credential and no organisation — it is what our own marketing site and AI answer engines read.
This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X POST https://api.zinndigital.com/v1/webhooks/nowpaymentsSigned in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
**Unauthenticated by design** — NOWPayments holds no Zinn® credential, so the `x-nowpayments-sig` HMAC-SHA512 over the raw request body *is* the authentication. Crypto holds no mandate, so this path only ever **confirms an async (invoice-ahead) payment** (ADR 0011 §6) — it never creates a chargeable mandate. The tenant is recovered from the `order_id` Zinn® packed on the outbound invoice, since the IPN carries no principal. Replays are expected and converge; a status Zinn® does not act on (still pending, or terminally failed) is acknowledged with 200 (a non-2xx would make NOWPayments retry it for days).
Response
| Name | Type | Required | What it is |
|---|---|---|---|
status | string<handled, ignored, duplicate> | Yes | `handled` — acted on. `ignored` — a valid event of a type Zinn® does not consume. `duplicate` — already processed; Stripe may stop redelivering. |
Errors this endpoint can return
400