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 Discord

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

todiscordDiscord
channel#ops

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 Discord

Send rich embeds to a channel via a connected bot or a channel webhook.

01
connect the bot
Add the ingestlayer bot to your server, or paste a channel webhook URL. Either credential is held in-region.
02
choose the channel
Select the target channel from the picker. Each connected channel is one reusable destination row.
03
shape the embed
The default embed carries the event name as its title and the payload as name/value fields; override with $event.* references.

in discorddelivered

┌─ #ops ─────────────────────────────────┐
│ ▎ payment.failed                        │
│ ▎ customer   acme-inc                   │
│ ▎ amount     €240.00                    │
│ ▎ reason     insufficient_funds         │
│ ▎ attempt    2                          │
└─────────────────────────────────────────┘

notes

Channel webhooks are limited to about 30 messages per minute; sustained volume should use the bot connection instead.
An embed allows at most 25 fields and 6000 total characters; larger events are summarized.
Mentions (@everyone, @role) are suppressed by default — opt in per pipeline if you actually want a ping.

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 →