From your own telemetry
Add payment.* attributes to spans and logs you already send. Onyx reads them. Provider and rail latency need span-level attributes.
Solutions
Watch payments the way you watch services.
Payments is a group of eleven pages built from the OpenTelemetry spans and logs your payment services already send, tagged with payment attributes. Only a payment ID is required.
What you get
The questions operators ask
Live Transactions, Transaction Explorer, Pending Payments and Failed Payments show what is moving and what is stuck. Rail Health, Provider Health and Merchant Impact show where.
Settlement in view
Settlement and Reconciliation counts the statuses you report. It does not reconcile against a bank or a provider.
How it works
Tag your telemetry
Add payment.id, and any of the other payment.* attributes you have, to your spans and logs.
Open Payments
The group sits in the sidebar with Overview, Live Transactions, Transaction Explorer, Rail Health, Provider Health, Merchant Impact, Pending Payments, Failed Payments, Settlement and Reconciliation, AI Payment Analyst and Payment Sources.
Read the summaries
Pages summarize up to 10,000 payments from the last seven days at most. The AI Payment Analyst is computed from your records with fixed rules. It is not a language model.
Tag one payment and see it.
A trial workspace is enough to try Payments.