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 Email

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

toemail.outEmail
toalerts@acme.com

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 Email

Send a transactional email to one or more recipients, addressable from event fields.

01
set the recipient
Enter a fixed address, or reference an event field like $event.payload.email to route per event.
02
write subject and body
Both accept $event.* templates. The body renders as plain text with an optional summary table of the payload.
03
confirm the sender
Mail goes out from mail@notify.ingestlayer.com with SPF and DKIM aligned. Set a reply-to if you want responses to reach you.

in emaildelivered

From:    mail@notify.ingestlayer.com
To:      alerts@acme.com
Subject: Payment failed — acme-inc (€240.00)

A charge failed for acme-inc.
  amount   €240.00
  reason   insufficient_funds
  attempt  2

notes

Outbound email is metered against a monthly quota that scales with your plan; over-quota sends are deferred, not dropped.
Sending from a fixed ingestlayer domain keeps deliverability high, but the From address is not your own domain.
Recipient addresses pulled from event fields are validated at send time; a malformed address dead-letters that delivery.

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 →