Payment Route Candidate

Overview

Payment Route Candidate describes an eligible payment path considered by the routing system before one route is selected for execution. Operationally, a candidate combines a provider, account, rail, currency or asset, region, method, settlement option, and any conversion or intermediary steps that satisfy mandatory constraints. The relationship with Payment Route Plan matters because one payment can appear as multiple requests, events, provider references, and ledger entries.

Payment Route Candidate is an eligible payment path considered by the routing system before one route is selected for execution. Its boundary with Payment Route must remain explicit so related records do not collapse into one status. Controls should evaluate hard constraints first, verify real-time health and capacity, calculate complete cost and timing, attach confidence, and record exclusion reasons. The record should retain candidate ID, component path, capabilities, constraints, health, limits, expected cost and latency, risk score, eligibility result, and evaluation time.

Payment Route Candidate should remain distinct from Payment Route, Payment Route Plan, and Payment Provider Risk, because each can represent a different stage, record, control, or financial outcome. It is a possible path, not a submitted payment and not evidence that the candidate was available at execution time.

When Payment Provider Risk is involved, the link must be auditable so operators can decide whether retry, repair, return, rerouting, or adjustment is safe. The operating model for Payment Route Candidate should connect design, operations, risk, finance, and support.

Teams should define who owns it, which payments it covers, and what evidence permits downstream action. Status verification should precede retry, reroute, repair, or adjustment.