Test Checkout.com webhooks
Checkout.com sends webhooks for payment lifecycle events such as approvals, captures, refunds, and voids, plus dispute events. Capture them on a free webhooks.cc endpoint to see exactly what Checkout.com sends, then replay deliveries or forward them to your local handler.
No credit card · 50 requests/day free · or get a guest URL without an account
Prefer a walkthrough? Read the local webhook testing guide.
Common Checkout.com webhook events
Checkout.com Workflows send JSON notifications with id, type, created_on, and data, signed in the cko-signature header.
| Event type | When it fires |
|---|---|
| payment_approved | Payment authorization was approved by the issuer |
| payment_declined | Payment authorization was declined |
| payment_captured | Authorized payment was captured |
| payment_refunded | Captured payment was refunded |
| payment_voided | Authorized payment was voided before capture |
| dispute_received | Cardholder opened a chargeback dispute |
Source: Checkout.com webhooks documentation.
How to test Checkout.com webhooks
- 1
Create a webhook endpoint
Sign in free with GitHub, Google, or email to create a persistent endpoint, or grab an instant guest URL at webhooks.cc without an account.
- 2
Point Checkout.com at your URL
Paste the endpoint URL into Checkout.com: Dashboard → Developers → Webhooks, or the Workflows API (POST /workflows).
- 3
Inspect what arrives
Each delivery appears live in the dashboard with method, headers, body, query parameters, and source IP.
- 4
Forward to localhost or assert in CI
Run whk tunnel <port> to forward webhooks to a local server, or use the TypeScript, Python or Go SDK to wait for and assert on deliveries in tests.
Checkout.com webhook authentication
| Auth header | cko-signature |
|---|---|
| Algorithm | HMAC-SHA256 |
| Verification in webhooks.cc | Capture deliveries to inspect raw signature material |
A hex-encoded HMAC of the raw body, keyed with the signature key set on the workflow's webhook action.
New to signature verification? Read the webhook signature verification guide.
Everything in one place
- Live dashboard: see deliveries the moment they arrive
- Forward to localhost with whk tunnel
- Replay any captured request to any URL
- Mock responses with custom status, headers, and body
- Forward to your servers, Slack or Discord
- TypeScript, Python and Go SDKs for CI assertions
- MCP server for AI coding agents
Checkout.com webhook questions
Each webhook action in a Checkout.com Workflow has a signature key. Compute a lowercase hex HMAC-SHA256 digest of the raw request body using that signature key and compare it with the cko-signature header. You can also configure an optional Authorization header on the workflow.
If your endpoint does not return a 2xx response within 10 seconds, Checkout.com Workflows retry the webhook with exponential backoff for up to 24 hours. Use the event id field to deduplicate repeated deliveries.
Create a free endpoint on webhooks.cc (sign in with GitHub, Google, or email, or use a guest endpoint without an account), then configure it as your webhook URL: Dashboard → Developers → Webhooks, or the Workflows API (POST /workflows). Every delivery shows up live in the dashboard with full headers, body, and query parameters. To hit a local server, run whk tunnel <port> and the CLI forwards each webhook to localhost.
Yes. Capture one real delivery from Checkout.com, then replay it to any URL from the dashboard, or run whk tunnel <port> to forward live deliveries to localhost. webhooks.cc has no built-in Checkout.com sample templates, but the Send button posts any payload and headers you paste in.
Checkout.com authenticates each delivery with the cko-signature header (HMAC-SHA256). A hex-encoded HMAC of the raw body, keyed with the signature key set on the workflow's webhook action. Capture a real delivery on webhooks.cc to inspect the exact header value, then implement the check in your handler.
Yes. A free account gets you persistent endpoints, 50 requests per day, 7-day retention, and full CLI, SDK, and MCP access, with no credit card. You can also try a guest endpoint without an account: up to 25 requests for 12 hours.
More providers
Your Checkout.com webhook URL is seconds away
Sign up free, create an endpoint, and point Checkout.com at it.
No credit card · or try without an account