How do I avoid alert spam on retries?

Filter on the attempt field, or set a dedupe window so repeated failures for the same charge collapse into one alert.

Can I only alert on high-value customers?

Yes. enrich.entity pulls MRR onto the event, then a filter keeps only the ones above your threshold.

Where does the decline reason come from?

Whatever you put in the reason field — usually the processor's decline code. ingestlayer passes it through untouched.

Monitor failed payments in Webhook

Catch failed charges the second they happen, with the customer, amount, and decline reason attached, so a billing problem becomes a message instead of a churn surprise.

01source

sourcesdk.eventTypeScript SDK

matchpayment.failed

02pipeline · 2 steps

01CTLfilter.matchamount ≥ 50.00 only
02ENRenrich.entitycustomer → plan · MRR · CSM

03destinations · 1

towebhook.outWebhook
urlhttps://api.acme.com/hooks

the event

You emit payment.failed with this shape. The TypeScript SDK keeps the call type-safe, and the event is stored whole — so every field below is available to the pipeline by name.

customer_idstring
emailstring
amountnumberminor units
currencystringISO 4217
reasonstringprocessor decline code
attemptnumber

emit it

From your code with the TypeScript SDK — or any language over the REST endpoint and signed webhook ingress.

emit payment.failed

import { ingest } from "@ingestlayer/sdk";

await ingest("payment.failed", {
  customer_id: charge.customer,
  email:       charge.receipt_email,
  amount:      charge.amount,
  currency:    charge.currency,
  reason:      charge.failure_code,
  attempt:     charge.attempt,
}, {
  idempotencyKey: `${charge.id}:${charge.attempt}`,
});

route it to Webhook

POST the processed event as JSON to any HTTPS endpoint you control.

01
set the URL
Any HTTPS endpoint. The processed event is delivered as a JSON body on POST.
02
choose auth
None, a bearer token, or HMAC signing. Signed requests carry an X-Ingestlayer-Signature header you verify with your shared secret.
03
confirm receipt
Return a 2xx within the timeout. Non-2xx responses trigger retries with exponential backoff before the delivery dead-letters.

in webhookdelivered

POST /hooks HTTP/1.1
Host: api.acme.com
Content-Type: application/json
X-Ingestlayer-Signature: t=1717000000,v1=9f86d08…

{
  "type": "user.signed_up",
  "payload": { "email": "ada@acme.com", "plan": "pro" }
}

notes

Endpoints must respond within 10 seconds; slower responses are treated as failures and retried.
Retries use exponential backoff for several attempts before dead-lettering — make your handler idempotent.
Verify the HMAC signature before trusting a payload; the raw body is signed, so compute the digest before JSON parsing.

questions

How do I avoid alert spam on retries?: Filter on the attempt field, or set a dedupe window so repeated failures for the same charge collapse into one alert.
Can I only alert on high-value customers?: Yes. enrich.entity pulls MRR onto the event, then a filter keeps only the ones above your threshold.
Where does the decline reason come from?: Whatever you put in the reason field — usually the processor's decline code. ingestlayer passes it through untouched.

build this pipeline or read the quickstart →