Four states of payment route readiness

A provider name in a catalogue does not mean a merchant can send production traffic to it. Route readiness needs a precise, shared vocabulary.

Known

The provider and its general market presence are documented. At this stage, the route is a research candidate only. Merchant-specific commercial acceptance, technical fit and production access are not yet confirmed.

Qualified

The route has been checked against the merchant context: entity, vertical, licences, geography, method, currency, traffic profile, volumes and operational constraints. Commercial requirements and important limitations are understood well enough to make an onboarding decision.

Integrated

The required pipeline lifecycle is implemented and tested: authentication, fields, statuses, callbacks, errors and any deposit, payout or refund operations in scope. Integration proves technical connectivity; it does not by itself prove production approval or current availability.

Active

The provider has approved the merchant, production credentials are assigned, the route is configured and the team is prepared to operate it. Monitoring, support and escalation paths exist. Only this state should be treated as ready for production routing.

Manage the transitions, not only the labels

Every change of state needs evidence and an owner. Qualification should point to current commercial and merchant-context checks. Integration should point to the tested lifecycle and environment. Activation should record production approval, credentials, monitoring and support readiness. Routes can also move backwards when a contract, limit, credential or technical condition changes. Add the verification date and next review point to every state. A visible transition history prevents a once-active route from remaining available only because nobody changed its label.

Known is research. Qualified is a fit decision. Integrated is technical readiness. Active is a production route.