ingestlayer/recipes

Track successful payments in Discord

Surface the payments that matter — a big invoice cleared, an annual renewed — without drowning the channel in every routine charge.

01source

sourcesdk.eventTypeScript SDK
matchpayment.succeeded

02pipeline · 2 steps

  • 01CTLfilter.matchamount ≥ 500.00 only
  • 02ENRenrich.entitycustomer → plan · account owner

03destinations · 1

  • todiscordDiscord
    channel#ops

the event

You emit payment.succeeded 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
  • amountnumberminor units
  • currencystringISO 4217
  • invoice_idstring
  • methodstringcard | sepa | invoice

emit it

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

emit payment.succeeded
import { ingest } from "@ingestlayer/sdk";

await ingest("payment.succeeded", {
  customer_id: charge.customer,
  amount:      charge.amount,
  currency:    charge.currency,
  invoice_id:  charge.invoice,
  method:      charge.payment_method_type,
}, {
  idempotencyKey: charge.id,
});

route it to Discord

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

  1. 01

    connect the bot

    Add the ingestlayer bot to your server, or paste a channel webhook URL. Either credential is held in-region.

  2. 02

    choose the channel

    Select the target channel from the picker. Each connected channel is one reusable destination row.

  3. 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

questions

How do I keep the channel quiet?
Filter on amount so routine charges pass silently to the warehouse, while only large payments reach a human.
Can I split by currency?
Branch on the currency field to route EU and US revenue to different channels or owners.
Will retries double-count?
No. The charge id as idempotencyKey collapses retries, so one cleared payment is one event.
build this pipelineor read the quickstart →

successful payments, routed elsewhere

more, into Discord