Talk to us

Add a payment rail

Short answer

Connect your bank’s systems to one payment core, then add rails as plug-in packs. Share validation, approvals, audit, monitoring and reconciliation while each rail supplies its own messages and rules.

For payment architects and delivery teams.

Test checklist

  • Route representative payments through the configured rules, including an unroutable case.
  • Validate the new rail’s message versions and rejection handling.
  • Repeat payments and responses. Check duplicate protection at shared bank interfaces.
  • Exercise maker-checker roles and limits. Retain the approval against the payment.
  • Follow acceptance, rejection and return cases through the core banking link.
  • Compare scheme, hub and core banking records, including a deliberate difference.
  • Interrupt the new connection and check service status, alerts and tracing.
  • Repeat acceptance, rejection and return scenarios on existing rails after shared-core changes.
  • Retain the tested configuration: rails, modules, adapters, rules, limits and roles.

With CordisPay

The CordisPay platform provides Aani, RTGS and SWIFT CBPR+ as standard rail packs. Payment lifecycle, routing, messaging, audit, Health, tracing, security and AI are built into one core. Each bank’s setup is configuration, not code.

Scope

  • CordisPay connects to core banking; it does not hold customer accounts.
  • Sanctions and AML screening stay in the bank’s own systems.
  • Each rail still needs its own test plan and official testing or certification.

Common questions

Does adding a rail mean replacing core banking?

No. CordisPay connects to your core banking system and does not hold customer accounts. The payment core sits between the bank's systems and the payment rails.

Which rails share the CordisPay core?

Aani instant payments, RTGS high-value payments and SWIFT cross-border payments using ISO 20022 CBPR+ are standard rail packs on the same core. The next rail is added as another plug-in pack.

What changes for each bank?

Rails and modules, bank adapters, rules, limits, roles and branding are configuration, not code. The core provides shared payment lifecycle, routing, messaging, audit, Health, tracing, security and AI that explains.

Can fiat and digital-asset rails use the same core?

The core's foundations let fiat and digital-asset rails run side by side, on the same controls, audit trail and monitoring. Each rail still needs its own messages, rules and test plan.

Related guides

Last reviewed:

Discuss your test plan.