Use Primer or Gr4vy as a starting point when payment operations needs to change routes through a workflow editor. Put Spreedly on the shortlist if engineering wants to bring payment calls and gateway connections together in an integration it owns. Review IXOPAY or Payrails when the same purchase needs to support reconciliation across several payment providers.
Follow a payment through routing and settlement
Check what the ecommerce storefront platforms on your shortlist permit at checkout before buying external orchestration. Some storefronts constrain which payment services can control the transaction route.
Compare ecommerce fraud prevention platforms if the unresolved decision is who reviews an order, handles fulfillment holds or reimburses eligible fraud losses. Carry the resulting risk decision through any approved payment route.
Once payments have cleared on multiple processors, chargeback management platforms can help teams compare who gathers the evidence and submits a response on each route.
| Platform | Routing control | Finance or token boundary | What to request in a quote |
|---|---|---|---|
| Primer | Workflow conditions, processor choice and configurable fallback | Authorization and capture can follow separate workflow events | Workflow, fallback and reconciliation entitlements |
| Spreedly | API-driven checkpoints and gateway routing | Define gateway events and the application handoff | Integration scope, gateway and included operations |
| Gr4vy | Visual no-code payment workflows across PSPs | Evaluate card data management and downstream exports | Required providers, workflows and data features |
| IXOPAY | Meta-connectors for routing, balancing and fallback | Connector-level settlement retrieval and reconciliation | Connector, reporting and reconciliation coverage |
| Payrails | Dashboard-configured routing and retries | Modular tokenization, reporting and reconciliation | Modules, integration and processor-specific scope |
Primer
Primer documents workflow conditions for directing authorization and separating capture into a later state-driven action. It also presents fallback to a backup processor. Consider it when payments staff need clear ownership of branching rules. Confirm the configured retry conditions, approval process and event identifiers for your processors. Quote the required routing, token and settlement features together. Official references include Product and scope, Plan or supporting details, Additional product details.
Spreedly
Spreedly's quickstart describes configuring a payment checkpoint that can authorize, capture, route to a gateway and retry a soft decline. This suits an engineering team that wants the payment decision embedded at a particular point in its application. Determine where you store the merchant order ID and which gateway response identifies the attempt. Get the quote and verify the payment methods and operations supported by your gateways. Official references include Product and scope.
Gr4vy
Gr4vy presents a visual layer for workflow changes, an agnostic provider approach and tools to manage card data. Include it when payments operations wants to own routing rules and engineering still owns the storefront. Check which roles may publish changes and which transaction exports finance can use for your chosen connectors. Confirm what the quote includes and how card data can be migrated. Official references include Product and scope.
IXOPAY
IXOPAY documents using meta-connectors for routing, cascading, balancing and fallback. Its connector manual separately describes data fetchers for reconciliation and provider settlement retrieval. Put it on the shortlist if finance and payment operations need to evaluate connectors as one purchase. Confirm which connectors provide settlement data and which formats your finance team will actually receive. Official references include Product and scope, Plan or supporting details.
Payrails
Payrails describes configurable routing, retries and payment workflows alongside modular reconciliation, tokenization and reporting capabilities. Consider it when a merchant needs payment operations and finance to share normalized records. Scope the modules in the quote and ask how partial captures, fees and refunds appear across processors. Evaluate any separate Merchant of Record offer independently because it changes the responsibilities in the purchase. Official references include Product and scope.
Choose the owner of each payment state
Give a pending authorization a different path from a confirmed recoverable decline. An alternate route can help if the original attempt clearly failed for a reason the new processor can address. A timed-out request can still settle. Establish how your checkout checks the first attempt and how finance sees each authorization, capture, refund and settlement under the same order. Ask each vendor to identify the records and identifiers it can provide for the specific processors you use. A storefront with one reliable processor and straightforward settlement may have little reason to introduce a new layer.
By Toolverly Editorial, with AI-assisted research and drafting.
Photo by SumUp on Unsplash. Read about our publication or send a correction.
