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.

Track successful payments in Email

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

toemail.outEmail
toalerts@acme.com

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 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 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 pipeline or read the quickstart →