Payment Span

Overview

Payment Span describes a timed unit of work within a distributed trace that represents one operation performed while processing or observing a payment request. Operationally, a span records its name, start and end time, status, attributes, events, parent context, and links to related asynchronous work so operations can be reconstructed across services. The relationship with Payment Request Trace matters because one payment can appear as multiple requests, events, provider references, and ledger entries.

Payment Span is a timed unit of work within a distributed trace that represents one operation performed while processing or observing a payment request. Its boundary with Payment Span ID must remain explicit so related records do not collapse into one status. Controls should use standard semantic conventions, safe attributes, stable operation names, correct parent or link relationships, error recording, and explicit correlation with payment IDs. The record should retain trace ID, span ID, parent span ID, service, operation, timestamps, status, attributes, events, links, and sampling information. Accountability for Payment Span includes current documentation, review dates, approval authority, and emergency rollback.

Payment Span should remain distinct from Payment Span ID, Payment Request Trace, and Payment Processing Step, because each can represent a different stage, record, control, or financial outcome. It is telemetry, not an authoritative payment stage or ledger entry, and its lifetime may cover only one technical operation.

Important risks include sensitive attributes, excessive cardinality, missing parent links, incorrect status, clock skew, spans left open, and sampling that removes critical failures. Post-incident findings should update controls and runbooks before the same failure recurs.

Controls should validate inputs server-side, authenticate external events, make irreversible actions idempotent, and reconcile provider, network, settlement, and ledger evidence. For Payment Span, this point supports the definition’s focus on timed unit of work within a distributed trace that represents one operation performed while processing or observing a.