api-reference/decision-engine-api-reference/payment-audit.mdx
Payment Audit is the operator-facing timeline view for a single payment or request.
Use it when you want to answer questions like:
The page is designed for exact lookups first and broad operator filtering second.
The page supports these filters:
payment_idrequest_idgatewayroutestatusflow_type15m, 1h, 12h, 1d, 1wUse an exact payment_id when you have it. If you only have a request trace, use request_id.
Payment Audit is always merchant-scoped by the authenticated JWT or API key. The route does not
accept scope or merchant_id query params.
The timeline is built from analytics events captured by the live request flows.
Current stages include:
gateway_decidedrule_appliedscore_updatedpreview_evaluatedrequest_read_failedvalidation_failedrequest_parse_failedscore_update_failedThe raw flow type remains visible as well, for example decide_gateway_decision,
decide_gateway_rule_hit, update_gateway_score_update, or routing_evaluate_advanced.
Payment Audit reads from the same ClickHouse analytics store used by the analytics surface.
The read path is split intentionally:
payment_id / request_id lookups read the raw analytics_domain_events timelineanalytics_payment_audit_summary_bucketsBoth views correlate events through the write-time lookup_key, which prefers payment_id and
falls back to request_id.
Relevant fields include:
merchant_idpayment_idrequest_idevent_stageroutegatewayrouting_approachrule_namestatuserror_codeerror_messagedetailsThe details field is shown as structured JSON when available.
When the dashboard profile is running, open:
http://localhost:8081/dashboard/auditwebsite/src/components/pages/PaymentAuditPage.tsxsrc/routes/analytics.rssrc/analytics/models.rssrc/analytics/service.rssrc/decider/gatewaydecider/src/feedback/gateway_scoring_service.rs