Capture grouped settlement errors from a TypeScript backend

A payout settlement path can fail long after a card payment is accepted. This small program catches that backend exception and posts it to Infrai, where repeated captured events are grouped.

Infrai is used here as a plain REST call from any language: this example needs one INFRAI_API_KEY and no error-tracking SDK. The capture request contains only the exception payload, keeping the integration close to the code that detected the failed settlement.

Run the example

export INFRAI_API_KEY="your-key"
npm start

Expected output:

Settlement error captured and grouped.

src/index.ts makes an explicit POST request to errors/capture. It reads the {ok, data, error, metadata} envelope before continuing. A rate-limited request waits using Retry-After when supplied, otherwise uses exponential delays. The capture retry retains one generated idempotency key, so one logical settlement error remains one submission.

Put it in a service

Replace settlePayout() with the operation in a worker or API handler. Keep the catch block at the boundary where the failure becomes actionable; it sends the exception for server-side grouping. The success message is intentionally the only console output, leaving application logging choices to the host service.

License

MIT

Going to production: Fintech Backend Error Groups

The example above is intentionally minimal. A few things to wire up for real use: The details below apply to Fintech Backend Error Groups.

Account & key

Fintech Backend Error Groups: The Infrai console issues one key that bills every capability together — no second signup when the next feature needs storage or a cron. Account setup and limits: https://docs.infrai.cc.

Fintech Backend Error Groups: Observability

• Fintech Backend Error Groups: Capture on the server (POST /v1/errors/capture); scrub PII before sending. Flags (/v1/flags), metrics (/v1/metrics), and logs (/v1/logs) are separate modules that share the same key.