The rip-and-replace assumption is the problem, not the ambition itself. Orchestration sits in front of core systems rather than replacing them. It validates, enriches, routes, and screens payments before they reach the estate you already have. The core stays untouched, and modernization happens on the layer above it.
Why the rip-and-replace assumption blocks the payment hub implementation approach
Every stalled orchestration conversation traces back to the same assumption about what the payment hub implementation approach requires. The assumption is that payments modernization means replacing the core, which means a program that spans years and consumes every discretionary technology dollar. Once framed that way, the conversation becomes a battle for budget rather than a design question, and the deferral pattern begins.
The assumption about the mechanics is wrong. Orchestration does not require touching the core, because the routing, validation, enrichment, and screening capabilities that define an orchestrated estate can run in a preprocessing layer in front of legacy systems. The legacy processing continues doing what it already does. The preprocessing layer handles everything modern that the core was never designed for.
Embedded Preprocessing is how a bank moves from Level 2 to Level 4 without replacing its core, and the operational reality behind that sentence is what makes the deferral pattern unnecessary.
Three routes for the implementation
The payment hub implementation approach breaks into three deployment routes, and each one suits a different starting condition. Choosing between them depends on internal capacity, existing infrastructure investment, and the timeline the bank needs to meet.
The three routes cover the range from fully managed to bank-operated:
- Payments as a Service delivers the entire preprocessing layer as a managed cloud service, so the bank consumes orchestration rather than building or running it.
- Cloud deployment with bank-managed operations gives the bank operational control over the preprocessing layer while removing infrastructure ownership.
- Hybrid deployment alongside an existing hub preserves prior payment infrastructure investment while adding orchestration capabilities the current hub does not deliver.
Route selection typically follows internal capacity rather than architectural preference. Banks with lean operations teams and near-term deadlines default to the SaaS route because it removes the operational lift.
Banks with mature payment operations and existing infrastructure prefer the hybrid or bank-managed routes. Low-code Studio underpins all three routes and delivers the configure-not-code layer that lets business teams change the estate without engineering releases.
Realistic timelines and what a payment hub implementation approach delivers in weeks
The timeline that makes the payment hub implementation approach viable inside a single budget cycle is measured in weeks rather than months. Embedded Preprocessing onboards in as little as a few weeks through low-code integration and self-service configuration.
The estate underneath does not change during that window, because the preprocessing layer sits in front of it rather than inside it. Weeks-not-months onboarding covers a specific and substantial capability set:
- ISO 20022 translation across inbound and outbound messages, so legacy systems process modern message formats without disruption.
- Validation and enrichment at ingest, so payments arrive at the core cleaner than they would through any translation layer.
- Embedded AML, KYC, and sanctions screening across every rail through one consolidated compliance path.
- Smart routing on bank-defined rules across ACH, wire, RTP, SWIFT, and SEPA, configured through policy rather than code.
- Cloud-native and API-driven integration into existing systems, so the deployment works alongside the estate rather than displacing it.
More than 75 banks worldwide already run on this capability set in production. The deployment model is not theoretical, and the timeline is not aspirational. Weeks-to-onboard is the operational reality for banks that have already taken the payment hub implementation approach past the deferral point.
Sequencing: start with the highest-exception rail, then scale
The payment hub implementation approach also raises a sequencing question that most banks answer incorrectly on instinct. Instinct says start with the highest-volume rail because it produces the largest visible impact.
The stronger case is to start with the highest-exception rail, because reducing exceptions delivers faster, measurable value than volume migration. The highest-exception rail is also where operations teams feel the pain most, which builds internal credibility for the broader rollout.
Starting with the highest-exception rail delivers three effects that volume-first sequencing does not. Exception reduction becomes measurable within weeks rather than quarters, which shortens the internal proof cycle.
Operations teams see relief on the workflow that hurts most, which converts skeptics into advocates for the next rail. And the exception patterns discovered during the first rail migration inform routing and validation rules for every subsequent rail, so each additional rail deploys faster than the one before.
The 2027 point matters for the sequencing conversation as much as it matters for the deployment one. A bank starting the payment hub implementation approach in Q4 2025 is ready for whatever the next regulatory wave brings in 2027.
A bank starting in 2027 is remediating the same architectural gap under time pressure, on a shorter runway, with a smaller team, against a harder deadline. The sequencing question and the timing question are the same question asked twice.
Your payment hub implementation approach without a transformation program
Volante’s Embedded Preprocessing modernizes payments without ripping and replacing. The capability set covers ISO 20022 translation, validation and enrichment, and embedded AML, KYC, and sanctions screening.
Smart routing runs on bank-defined rules across every rail, and integration is cloud-native and API-driven, connecting to existing systems. Onboarding takes as little as a few weeks through low-code integration and self-service configuration. More than 75 banks worldwide already run on it in production today.
The next regulatory wave arrives in 2027. Every quarter of delay makes the reallocation case harder to build than the previous quarter. Every rail added without orchestration compounds the operational cost of the ones already in place.
Talk to Volante about Embedded Preprocessing to modernize your payment estate without touching the core. Ask about Payments as a Service for the managed cloud route with no operational lift.
