Choosing the best provider for domestic and cross-border payment processing depends on an institution’s markets, existing infrastructure, payment volumes, and operating model. Leading providers differ in the payment systems and networks they support, their approach to ISO 20022, architecture and deployment options, resilience, and how easily new capabilities can be introduced alongside existing infrastructure.
The market includes specialist payment technology providers alongside vendors with broader banking technology portfolios. As payment hubs become more composable, banks also have greater flexibility to select payment processing technology independently from their core banking provider.
This guide compares Volante Technologies, FIS, Fiserv, Finastra, ACI Worldwide, Temenos, TCS BaNCS, Oracle, and CGI against the factors that matter when processing domestic and cross-border payments.
Key takeaways
- The best provider will depend on the payment systems, markets, transaction types, and operating model an institution needs to support.
- Domestic and cross-border processing can be consolidated onto common payment hub infrastructure, reducing duplication between separate processing environments.
- ISO 20022 capabilities should be assessed according to how well structured data is preserved and used throughout processing, rather than message compatibility alone.
- Cloud-native architecture can support scalability and more flexible deployment, but buyers should also assess resilience, hosting options, and cloud concentration risk.
- Composable architecture can allow institutions to introduce or replace individual capabilities progressively, while preserving other existing payment technology.
- Total cost of ownership should account for implementation, integration, infrastructure, maintenance, scheme changes, and operational resources, rather than licensing or transaction costs alone.
- The strongest providers combine broad domestic and cross-border connectivity with a common processing layer, helping institutions add payment methods and markets without creating additional processing silos.
How do you compare cross-border and domestic payment providers?
A useful comparison should consider payment coverage, ISO 20022 capabilities, architecture, deployment and resilience, and total cost of ownership.
A modern payment hub can centrally process incoming and outgoing payments across real-time, batch, high-value, and cross-border transactions. The Gartner® Market Overview for Banking Payment Hub Platforms also points to composable architectures, cloud processing, payment innovation, AI, and resilience as important developments shaping the market. Volante Technologies was also recognized as a Leader in the Gartner® Magic Quadrant™ for Banking Payment Hub Platforms, reflecting its strength in both ability to execute and completeness of vision.
| Provider | Payment coverage | Architecture and ISO 20022 | Deployment and resilience | Best suited to |
|---|---|---|---|---|
| Volante Technologies | Domestic, instant, high-value, and cross-border payments, including SWIFT gpi, Fedwire, CHIPS, ACH, RTP, FedNow, SEPA, Faster Payments, Visa B2B, Mastercard Send, Ripple, digital currencies, and other payment networks | ISO 20022-native, cloud-native, composable platform with low-code configuration and intelligent routing and orchestration | PaaS/SaaS, public, private, and hybrid deployment, with multi-cloud resilience | FIs and PSPs seeking to modernize and consolidate domestic, instant, high-value and cross-border payments on a single cloud-native platform while maintaining flexibility across payment systems, networks, and deployment models |
| FIS | Real-time, high-value domestic, international, ACH, and batch payments | Open Payment Framework provides an ISO 20022-based foundation with reusable services and modular payment components | Modular managed modernization approach | Institutions seeking broad domestic and international payment capabilities through a modular payment framework |
| Fiserv | Instant, high-value, domestic, and cross-border payments | Centralized platform supporting ISO 20022 processing and integration with existing applications | On-prem, cloud, or managed service, with the option to deploy alongside existing technology | Institutions seeking to centralize multiple payment types, with a choice of on-prem, cloud, or managed-service deployment |
| Finastra | Real-time, high-value, mass, and cross-border payments across multiple markets | Global PAYplus is an ISO 20022-native, modular payment hub | Cloud-agnostic and multi-cloud deployment options | Institutions seeking a multi-country payment hub spanning real-time, high-value, mass, and cross-border processing |
| ACI Worldwide | Domestic and regional RTGS/wire, instant, ACH, and SWIFT cross-border processing | Enterprise payment architecture supporting ISO 20022 and orchestration around existing processing environments | Cloud and on-prem deployment options | Institutions seeking to support multiple account-to-account payment types across cloud or on-prem environments |
| Temenos | Domestic and cross-border payment processing, including SWIFT-related requirements | Payment hub capabilities supporting ISO 20022 and CBPR+ | Part of the wider Temenos banking technology portfolio | Banks seeking an ISO 20022 payment hub that can operate with Temenos or other core banking environments |
| TCS BaNCS | Domestic, cross-border, real-time, direct debit, and SWIFT gpi payments across multiple countries and currencies | ISO 20022-native, component-based architecture with APIs and SWIFT certification | Designed for integration across multiple geographies, entities, and market infrastructures | Institutions requiring domestic and cross-border processing across multiple countries, currencies, and entities |
| Oracle | Domestic high-value, ACH, real-time, and incoming and outgoing SWIFT payments | Unified payment hub based around an ISO 20022 data model | Available within Oracle’s wider banking and cloud technology environment | Institutions seeking a unified payment hub for domestic, real-time, and cross-border processing, including SWIFT connectivity |
| CGI | Real-time, domestic wire and ACH, high-value, SWIFT, and cross-border payments | Modular, API-enabled, ISO 20022-native platform | On-prem, SaaS, private cloud, and multiple public cloud environments | Institutions seeking modular payment processing with a broad choice of on-prem, SaaS, private-cloud, and public-cloud deployment models |
What should you look for in a cross-border payments provider?
Start with coverage, then establish how consistently the provider can process those different payment types. Depending on the institution, requirements may span SWIFT for cross-border messaging, Fedwire and CHIPS for U.S. high-value payments, SEPA in Europe, domestic ACH systems, instant payments, card-based services, and alternative cross-border networks.
A long list of connections is less useful if each requires separate infrastructure, workflows, or operational tooling. Buyers should therefore determine whether payment types can share validation, transformation, routing, exception management, compliance integrations, and operational controls.
Buyers should also evaluate how providers are applying AI to areas such as exception management, payment investigations, operational monitoring, and routing decisions. As payment volumes and complexity continue to increase, intelligent automation can help improve efficiency while reducing operational risk.
ISO 20022 is another important differentiator. A platform may be able to receive or convert an ISO 20022 message without using the structured information throughout the payment lifecycle. Buyers should therefore assess how data is preserved through processing, whether formats can be configured as requirements change, and how richer data can be made available to downstream systems.
Resilience should also be assessed at architecture level. Disaster recovery, infrastructure dependencies, failover arrangements, hosting locations, and cloud concentration risk all influence whether payment processing can continue when an underlying service becomes unavailable. Volante’s Multi-cloud Resiliency Service, for example, provides cross-cloud failover to a secondary cloud environment, extending resilience beyond a single cloud provider.
Finally, total cost of ownership should reflect the complete operating environment. Implementation, integration, infrastructure, maintenance, scheme updates, support, and manual intervention can all influence the economics of a platform over time.
Networks, banks or cloud-native platforms: which type of provider is right?
Most institutions will need a combination of payment networks, banking relationships, and processing technology because each performs a different role in moving money across borders.
SWIFT provides financial messaging and connectivity, while correspondent banking relationships provide access to accounts, currencies, liquidity, and settlement. A payment hub sits within the institution’s processing environment, managing how instructions are validated, enriched, screened, routed, and passed to the appropriate network or counterparty.
Newer cross-border services add further options. Volante’s Cross-border Payments Solution supports SWIFT gpi alongside Visa B2B, Mastercard Send, Ripple, digital currencies, blockchain networks, and alternative payment methods through a common platform. The value for a financial institution is the ability to incorporate different routes within a broader processing environment, rather than building a new operational silo for every service.
This makes orchestration an important consideration. Intelligent routing can give institutions greater scope to select payment paths according to defined factors, such as availability, cost, speed, or business rules. The technology still depends on the institution’s connectivity, counterparties, liquidity arrangements, and the capabilities available for a particular transaction or market.
How cloud-native processing changes cross-border economics
Cloud-native processing changes the cost model by reducing dependence on institution-owned infrastructure and allowing computing resources to respond more flexibly to transaction demand. It does not, by itself, guarantee a lower total cost of ownership.
Traditional payment environments can require dedicated infrastructure and specialist resources for different systems, alongside ongoing expenditure on maintenance, capacity, integrations, and scheme changes. Cloud and managed-service models can transfer some infrastructure and platform responsibilities to the provider, while allowing capacity to scale with demand.
Cloud-native payment hubs can also scale horizontally to respond to peaks in real-time payment volumes. Composable microservices provide another option for modernization, allowing individual components to be introduced, upgraded, or replaced without requiring a wholesale platform change. These developments are among the architectural shifts covered in the Gartner® Market Overview for Banking Payment Hub Platforms.
Actual TCO will still depend on transaction volumes, migration requirements, integration complexity, customization, service levels, and the division of operational responsibilities between the institution and provider.
Resilience belongs in that calculation too. A cloud deployment can still create concentration risk if payment processing depends on a single provider. Multi-cloud architecture can extend disaster recovery across cloud providers, giving institutions another option for maintaining processing continuity during a major provider-level outage.
Why handle domestic and cross-border payments on one platform?
A common platform can reduce duplicated infrastructure and provide more consistent processing across payment types, even where the underlying schemes, currencies, and settlement arrangements remain different.
Validation, message transformation, routing, monitoring, exception handling, and core-system integration are required across many domestic and international payments. Centralizing these capabilities can reduce the need to maintain separate processing environments for each payment type, while APIs can make multiple payment methods available to connected systems through a common processing layer.
This becomes particularly relevant as payment portfolios expand. Real-time domestic and cross-border payments, ISO 20022, and emerging forms of money are adding new requirements to payment infrastructure. A composable platform can give institutions a way to introduce capabilities progressively, rather than treating every new payment method as a separate infrastructure project.
For Volante, this is reflected in a single platform designed to support domestic, cross-border, and instant payment processing. Its payment infrastructure spans systems including ACH, Fedwire, RTP, SWIFT, FedNow, SEPA, CHIPS, card networks, and tokenized deposits. Its regional platforms also support domestic schemes such as Faster Payments, Bacs, and CHAPS in the UK, alongside cross-border connectivity.
The approach can also be seen in practice. British Arab Commercial Bank (BACB) is using Volante Payments as a Service to modernize its payments infrastructure and automate processing across SWIFT, CHAPS, Faster Payments, Bacs, and internal transfers. Bringing a wider range of payment schemes into a single integrated platform gives the bank a foundation for managing domestic and cross-border flows without maintaining a separate processing environment for every payment system.
For institutions assessing providers, this ability to manage different payment types through common infrastructure can reduce duplication, while preserving the specific processing, connectivity, and compliance requirements of each.
Shortlisting: a checklist for your RFP
A useful RFP should test how each provider will operate within the institution’s actual payment environment:
- Which domestic, high-value, instant, and cross-border payment systems and networks are supported today?
- Which connections and capabilities are available out of the box, and which require additional development?
- How does the platform preserve and use ISO 20022 data throughout processing?
- Can different payment types share validation, routing, exception management, operational tooling, and integrations?
- Can individual components be introduced alongside existing or third-party payment technology?
- Which SaaS, PaaS, cloud, hybrid, and on-prem deployment models are available?
- How does the resilience model respond to the failure of a cloud provider, region, data center, or other infrastructure?
- Where can the platform and its data be hosted, particularly where local data-sovereignty requirements apply?
- Who manages scheme updates, regulatory changes, maintenance, and underlying infrastructure?
- How are fraud, AML, sanctions, FX, liquidity, and other external services integrated?
- What comparable implementations can the provider demonstrate?
- How will total cost of ownership change as transaction volumes, payment types, and geographic coverage grow?
Implementation, support location, hosting arrangements, and data sovereignty can be just as important as the functional checklist. Buyers should therefore assess not only what a platform supports, but how it will be implemented, operated, supported, and scaled within their particular regulatory and infrastructure environment.
Frequently asked questions
The best provider will depend on the institution’s markets, existing infrastructure, and operating model. However, for FIs and PSPs looking to combine domestic and cross-border processing on modern payment infrastructure, Volante Technologies stands out for the breadth of capabilities it brings together on a single platform.
Its coverage spans domestic, instant, and high-value payment systems alongside cross-border connectivity through SWIFT gpi, Visa B2B, Mastercard Send, Ripple, digital currencies, and alternative payment networks. This is combined with ISO 20022-native processing, cloud-native and composable architecture, low-code configuration, intelligent routing and orchestration, and multi-cloud resilience.
That combination makes Volante particularly relevant for institutions looking to modernize payment processing without creating separate infrastructure for each new payment type, network, or market.
There is no universally cheapest enterprise provider because public pricing does not capture the complete cost of running a payment platform. Institutions should compare total cost of ownership across implementation, infrastructure, integration, upgrades, support, operational resources, and transaction growth.
A lower initial platform or transaction cost may therefore produce a different result once integration, infrastructure, maintenance, and internal resources are taken into account.
Alternative cross-border networks can provide additional routes for particular corridors, currencies, or transaction types, but they do not necessarily perform the same role as SWIFT.
Institutions should compare reach, settlement models, currencies, counterparties, data, and integration requirements. A processing platform capable of connecting to multiple networks can make it easier to expand those options over time.
Not necessarily. Modern payment hubs can process domestic, high-value, instant, and cross-border transactions through common infrastructure, while retaining the rules, formats, and connectivity required by individual payment systems.
Composable architecture can also allow institutions to introduce new components progressively and operate them alongside existing or third-party payment technology. This can give banks more flexibility over how quickly they consolidate their payment environment.
Yes. Payment processing needs to operate continuously, making resilience an important selection criterion. Buyers should assess availability, disaster recovery, infrastructure dependencies, hosting locations, and multi-cloud capabilities, as well as how processing can continue if an underlying service becomes unavailable.
For cloud deployments in particular, the assessment should consider whether disaster recovery protects against a regional failure within one cloud or extends across separate cloud providers. Volante’s Multi-cloud Resiliency Service is designed for the latter, providing cross-cloud failover for payment processing.
