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 Webhook

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

towebhook.outWebhook
urlhttps://api.acme.com/hooks

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 Webhook

POST the processed event as JSON to any HTTPS endpoint you control.

01
set the URL
Any HTTPS endpoint. The processed event is delivered as a JSON body on POST.
02
choose auth
None, a bearer token, or HMAC signing. Signed requests carry an X-Ingestlayer-Signature header you verify with your shared secret.
03
confirm receipt
Return a 2xx within the timeout. Non-2xx responses trigger retries with exponential backoff before the delivery dead-letters.

in webhookdelivered

POST /hooks HTTP/1.1
Host: api.acme.com
Content-Type: application/json
X-Ingestlayer-Signature: t=1717000000,v1=9f86d08…

{
  "type": "user.signed_up",
  "payload": { "email": "ada@acme.com", "plan": "pro" }
}

notes

Endpoints must respond within 10 seconds; slower responses are treated as failures and retried.
Retries use exponential backoff for several attempts before dead-lettering — make your handler idempotent.
Verify the HMAC signature before trusting a payload; the raw body is signed, so compute the digest before JSON parsing.

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 →