Connect to a PayFac, TSYS, Mercury, Heartland, FluidPay, Inspire, NMI, Authorize.net, and hundreds more from a single integration. You decide which processor handles which transaction. Value.IO executes it — no custom connector for each processor, no rebuilding your integration when your acquiring relationships change.
Most payment infrastructure makes routing decisions for you, or forces you to build and maintain custom connector code for each processor. Value.IO works differently. You pass three things in the API call: the amount, the card vault ID, and the destination processor. Value.IO executes it. The routing logic lives entirely in your code — not in a rules engine, not in a dashboard configuration. You use the card intelligence Value.IO provides to make your decisions, then tell us where to send it.
Value.IO's routing network spans native direct connections, gateway integrations that unlock downstream processor access, and an extended network of hundreds of additional destinations via Inspire Commerce. Custom endpoint coding is available for any destination not yet in the network.
Routing across multiple processors is only operationally useful if you can see what's happening across all of them. Value.IO includes the reporting and webhook infrastructure to manage a multi-processor environment without building a second layer of tooling.
Event notifications from all connected processors surface through a single endpoint. One webhook configuration covers every processor in your routing setup. No per-processor webhook management, no aggregation logic.
Transaction data from every processor connection aggregates into a single reporting view. Reconciliation, volume analysis, and audit trails span your full processor network without exporting and joining separate datasets.
The Value.IO dashboard will surface per-processor network response times, authorization success rates, and enhanced card intelligence, including card type and issuing bank address. Enough visibility to make processor weighting decisions from data, not instinct.
Value.IO is built for PayFac-model platforms. Sub-merchant onboarding and account management are native to the architecture, not bolted on. Routing to merchant-specific processor accounts is a first-class operation, not a workaround.
The infrastructure handling your multi-processor routing meets PCI DSS Level 1 requirements: the highest level of payment security certification.
Scenario
You run a SaaS platform with 50 merchants. Each merchant has their own acquiring relationship with a different processor — Heartland for one, TSYS for another, Mercury for a third.
You integrate Value.IO once. When a transaction comes in, your code reads the merchant identifier, determines the correct destination, and passes it in the API call. Value.IO routes it. No per-processor SDK. No separate integration for each acquiring relationship. Adding a new merchant with a new processor means updating your routing logic, not your codebase.
Scenario
You've negotiated better interchange rates with different processors for different card types. Heartland gives you better rates on regulated debit. TSYS performs better on premium credit. You want to route each transaction to the right destination automatically.
Value.IO returns card intelligence on every stored card — card type, regulated flag, issuing country, card category. Your code reads it and sets the destination in the API call accordingly. Regulated debit goes to Heartland. Premium credit goes to TSYS. Value.IO executes whichever destination you specify. No rules engine. No dashboard configuration. Your logic, running in your code.
Scenario
One of your merchants wants fine-grained control: domestic transactions to their primary processor, international cards to a second processor with better cross-border rates, and high-value transactions above $5,000 to a third processor with a lower fee structure at that tier.
Your routing code reads the card's country of issuance and transaction amount from the Value.IO card intelligence response, applies your merchant's rules, and sets the destination. Value.IO routes it. The merchant has three processor relationships active under one Value.IO integration. Adding or changing a processor relationship doesn't require a code change — just a destination update in your routing logic.
Scenario
Your primary processor experiences degraded response times. You need transactions to keep moving without manual intervention or a code deployment.
Your routing logic monitors processor response and adjusts the destination parameter accordingly. When your primary shows latency above threshold, your code routes to the backup processor instead — same Value.IO API call, different destination. No re-integration. No downtime. You built the failover logic once; it runs automatically whenever conditions trigger it.
Scenario
You operate a national mobile ordering platform serving hundreds of venues. Independent locations need merchant accounts — they don't have existing processor relationships. Regional and national brands bring their own: Heartland, Mercury, First Data, Authorize.net, NMI. Every venue is a different destination. Every customer sees one ordering experience.
You integrate Value.IO once. Value.IO Instant provides bank-underwritten merchant accounts for the independents. For the nationals, you pass each brand's processor destination in the API call. A customer ordering at venue A and venue B in the same session triggers two separate transactions, each routed to the correct destination. Millions of dollars a month flow through six acquiring destinations from a single integration.