PNTR
All guides

Webhooks guide

Inspect Creem test-mode payment webhooks

Creem separates test and production data. A PNTR capture endpoint lets you complete a test checkout, see the resulting payment lifecycle event, and confirm the exact payload before implementing access changes.

Explore PNTR's online webhook tester
Create the Creem endpoint

Test-mode webhook URL

https://yourname.pntr.dev/creem

Setup

  1. 1

    Create a dedicated capture URL

    Create a PNTR webhook hostname and use a clear path such as https://yourname.pntr.dev/creem. Do not reuse a production webhook destination for inspection.

  2. 2

    Register it in Creem test mode

    Open the Developers webhook area in Creem's test environment and register the PNTR HTTPS URL. Keep the generated webhook secret private for your later application handler.

  3. 3

    Complete a test checkout

    Create a test-mode product and checkout, then complete the payment with Creem's test data. Test and live environments are isolated.

  4. 4

    Inspect the payment event

    Open PNTR and inspect eventType, object, created_at, and the creem-signature header. Creem also lets you resend webhook events from the Developers area.

  5. 5

    Implement the production receiver

    Verify the signature against the raw body, deduplicate by event ID, and only then grant, update, or revoke access. Register the deployed URL separately in Creem's live dashboard.

Before you ship

PNTR intentionally shows captured headers and bodies, so use synthetic test customers only. Creem signs the raw payload with HMAC-SHA256 in creem-signature; parsing and re-serializing JSON before verification can change the signed bytes.

Primary documentation