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 Telegram

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

totelegramTelegram
chat@oncall

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 Telegram

Message a person, group, or channel through a connected bot.

01
connect a bot
Create a bot with @BotFather and paste its token. We register the webhook and verify it in-region.
02
start a chat
Send /start to the bot from the target chat — or add it to the group/channel — then pick the chat from the list.
03
format the text
Messages use MarkdownV2; the default template bolds the event name and lists fields. Reserved characters in field values are escaped for you.

in telegramdelivered

oncall
*support.ticket.created*
ticket    T-4821
subject   API returning 500s
tier      enterprise
urgency   critical

notes

Telegram caps a bot at roughly 30 messages per second overall, and one per second to a single chat.
The bot must be added to a group — and promoted to admin for a channel — before it can post.
MarkdownV2 requires escaping characters like _ * [ ] ( ); ingestlayer escapes field values, but custom templates are your responsibility.

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 →