Payment Analytics

Payment analytics is the practice of measuring payment records to answer operating questions: how many payments succeed, how fast they settle, what they cost, and where they fail. A good setup ties each payment to an order, so finance and engineering read the same numbers.

Metrics that matter

• Payment success rate. The share of attempts that complete. Split it by amount, asset and time of day to find patterns.
• Time to settle. The delay between a payment request and a completed payment. See transaction speed.
• Outcome mix. How many payments end as completed, failed or expired. A high expired share often means the invoice window is too short or the checkout is confusing.
• Cost. The total of routing and platform transaction fees, compared with your previous payment mix.
• Volume and ticket size. Totals and averages by day, product or customer segment.
• Refund and dispute load. On cards this includes the chargeback ratio. On Lightning, completed payments are final, so the dispute line mostly becomes refunds that you send.

Lightning-specific data

Card analytics start from authorisation approvals. Lightning analytics start from the invoice. Each payment has an identifier and a payment hash, and a status that moves from pending to a final state. Because settlement runs 24/7, reports should not assume banking hours or batch cut-offs. Two further sources matter for operators: the node's own forwarding and channel data, and public network data on capacity and liquidity.

From metrics to decisions

Start with one question, such as "why do 4% of invoices expire?", and pick the two or three fields that answer it. Review the numbers on a fixed schedule. Segment before you average, because one slow asset or one large ticket size can hide inside a healthy overall rate. Keep the order ID on every record so a number can always be traced back to a real payment.

How Amboss handles payment analytics

Amboss began as a Lightning analytics company. Amboss Space launched in 2021 as a Lightning Network explorer and analytics platform, and the company says it has collected data on how money moves through the network for more than five years. Later products, such as the Magma liquidity marketplace, were built on what that data showed. Amboss still publishes live capacity and node metrics on Space.

For payments and nodes today:

• Per-payment records. With Amboss Payments, each payment has a transaction ID that you match to your order. Webhooks fire on every status change, and you can pull transaction history for reconciliation.
• Platform figures. Amboss reports production data in its own content, for example a median live payout time of 2.8 seconds in September 2026, with nine in ten payouts under 12 seconds.
• Node reporting on Rails. Rails includes a dashboard to track node performance, earnings and revenue opportunities. See performance reporting.
• Audit reports. Reflex produces exportable audit reports for compliance teams, covering sanctions screening and OFAC channel checks.