Webhook workflows

Add PushTheSales without replacing your webhook backend.

Your backend already processes payment webhooks. Add PushTheSales for notifications and analytics while keeping that processing clear and observable.

Connect it to your backend Read the setup steps ↓
SOURCEYour payment provider
PushTheSalesReceive · normalize · forward
Your webhook backendWebhook processing stays in place

Add another provider destination, or forward through PushTheSales when one URL is available.

Illustrative routing diagram · compatible receivers required
THE PROBLEM

Does this sound familiar?

  • Your backend already owns the provider webhook URL.
  • Changing routes without visibility risks losing events.
  • You need to know whether PushTheSales changes the payload your server receives.

Your existing integration stays in the loop while PushTheSales adds analytics and alerts.

THE SETUP

How to make it work.

  1. Choose the provider path.

    Stripe, Polar and Creem can often send to an additional endpoint. Apple provides one production URL and one sandbox URL per app, so another receiver may require forwarding through PushTheSales.

  2. Add PushTheSales beside the existing endpoint.

    When the provider supports it, create a second destination with the PushTheSales ingestion URL and leave the backend destination enabled. Select the provider’s recommended event set.

  3. Use forwarding for a single-URL provider.

    Set the provider URL to PushTheSales, then add your backend as a forwarding destination. Choose the correct provider and environment before testing.

  4. Check the receiver contract.

    Most providers’ original body and headers are forwarded. Apple is forwarded as decoded JSON, not the original signed Apple envelope. A receiver that verifies Apple’s JWS must be adapted before switching.

  5. Test with duplicate-safe logic.

    Send a destination test and a real sandbox event. Retries and replay can repeat an event, so use its provider event ID for idempotency. Watch response status, latency and attempts during live traffic.

IN PRACTICE

Choose between a second destination and an intermediary.

Multiple direct endpoints.

When supported, configure both your backend and PushTheSales directly. Each system gets its own independent delivery record.

Forwarding from PushTheSales.

Forwarding sends the event to a compatible receiver URL. Delivery history exposes failures, and retries provide recovery. A rule can be tested before it carries production events.

Signatures have two layers.

The provider may sign the original event, and PushTheSales signs the forwarded delivery with X-PushTheSales-Timestamp and X-PushTheSales-Signature. Verify the HMAC at your receiver where applicable.

Questions about this setup.

Can my backend keep its own destination?

Yes when the provider supports multiple endpoints. Add PushTheSales as another destination.

What about Apple’s one production URL?

Point Apple at PushTheSales and forward to a receiver that accepts decoded JSON.

Can retries duplicate orders?

They can deliver an event more than once. Use the provider event ID for idempotency at the receiver.

Can I inspect failed forwarding?

Yes. Delivery history includes attempts, HTTP status, latency and errors. Retry after fixing the receiver.

PUT IT INTO PRACTICE

Your existing integration stays in the loop while PushTheSales adds analytics and alerts.

Start in PushTheSales, then follow the setup for your provider.

Connect it to your backend