See exactly what Paddle sent your billing code.
Paddle notifications drive subscription state, and the gap between what you think arrived and what actually arrived is where billing bugs live. SignalBin gives Paddle a stable URL to notify, then keeps the delivery so you can read it, share it, and send it again.
Stable notification URLRaw body and header captureShared with the whole workspace
Workflow
How the debugging loop goes.
01
Create a receiving URLAdd an endpoint and register its URL as a Paddle notification destination for your sandbox or live account.
02
Run the billing flowComplete a checkout, change a plan, or let a renewal fire. Each notification Paddle sends is stored with its full body and headers.
03
Compare deliveriesFilter webhook history by endpoint and method to line up the sequence of notifications behind a single subscription change.
04
Hand it to a teammateWebhook history belongs to the workspace, so support and engineering open the same record instead of pasting payloads into chat.
Details
Worth knowing before you wire it up.
Sandbox and live stay separateGive each Paddle environment its own endpoint. Nothing has to be renamed or moved when you promote an integration to live.
Evidence outlives the sessionA captured notification is still there after the terminal window is closed, which is what makes it useful when a customer reports the problem two days later.
Sensitive values are redacted at restAuthorization, cookie, token, and signature-style header and field names are stored as
[redacted], so a shared workspace record is not a secret store.FAQ
Common questions.
Does SignalBin verify Paddle signatures for me?
No. SignalBin captures the request and can relay it to your service, where your own verification runs. Verification stays in your code.
Can I replay a Paddle notification?
Yes. Replay sends the stored copy of the request to your configured destinations, which is useful for re-running a handler after a fix.
Is there a size limit on a notification?
Request bodies over 20 MiB are refused before storage. Billing notifications are far below that.
Start with one endpoint.
Send a request, open the payload, and see exactly what your provider delivered.