Payment orchestration: routing, retries and orders
Payment orchestration connects routing, provider results and reconciliation; this guide shows the decisions and records a retailer must control.
- Published
- Last updated
Payment orchestration selects a payment provider for each transaction and applies routing and retry rules. Its records keep the resulting attempts connected to the order. It helps retailers coordinate several payment connections through one integration. The processors still handle their routed transactions, and the retailer still needs a confirmed result before releasing an order.
The extra layer is useful when you need control across providers. If one provider already supports your payment methods and markets, orchestration adds operating work that needs a clear purpose.
What payment orchestration controls
A payment orchestrator controls which connected provider receives a payment and what happens after its response. A gateway transmits payment requests. A processor handles their processing, while an acquirer provides the merchant’s card-acceptance relationship. A merchant account receives card-payment proceeds under that arrangement. One supplier can combine several of these roles.
A payment hub is a central point for payment activity. The name alone doesn’t establish whether it routes retail card transactions, initiates bank payments or only consolidates records. Compare the functions and contracts behind the label.
| Approach | Who selects the route? | What the retailer controls |
|---|---|---|
| One-provider checkout | The store sends payments to its selected provider | Checkout settings and the provider’s available payment options |
| Gateway | The integration and gateway configuration determine the destination | The configured connection, with routing features dependent on that gateway |
| Payment orchestration | The orchestration layer evaluates rules across connected providers | Permitted destinations, initial routing, eligible retries and attempt records |
| Central payment hub | Depends on the hub’s documented services | Only the routing, initiation or reporting functions included in the product |
For the underlying provider roles and selection criteria, use the ecommerce payments guide. Adding another payment method to one provider’s checkout doesn’t by itself establish multi-provider orchestration.
“Intelligent payment routing” or “smart payment routing” describes how a product chooses a destination. A declared rule might send a currency to a contracted processor that supports it, with a default route for other transactions. The permitted routes must also support the merchant’s region and channel.
Stripe’s orchestration rules use conditions such as currency and card country, applying the first matching action. Spreedly’s routing documentation describes conditional branches and percentage-based traffic splits. A vendor’s undisclosed optimisation model doesn’t tell you which route a particular transaction will take. Require an explanation or record of the actual decision before relying on it operationally.
Follow a payment across providers
Keep one order identity across the payment’s route, authorisation and capture, with separate records for each attempt. Authorisation reserves an approved amount. Capture requests collection of that authorised payment. A store must distinguish those stages when deciding what it can promise the customer.
Consider fictional order RET-208 for a $180 basket. The retailer has contracted two processors that support its online card transactions. Its chosen flow uses authorisation followed by capture.
- The customer chooses a card at checkout. Approved payment fields send the card details to the payment service and return a payment-method token.
- The store creates the payment for RET-208 and $180. It records a request identifier for duplicate protection.
- The orchestrator evaluates the routing rule and sends the authorisation to Processor A. The attempt gets its own reference.
- Processor A confirms authorisation. The store records the authorised amount and the processor reference, without marking the payment captured.
- The retailer’s capture action uses the successful authorisation. The store waits for the documented capture result before marking the order paid.
- The store links the successful payment to RET-208. Finance later matches the processor’s payout records to the captured transaction.
Spreedly’s processing guide documents token collection and separate authorisation or purchase steps. Capture completes a prior authorisation. The available sequence depends on the selected connection.
Keep the order reference beside the orchestrator’s payment ID and each processor transaction ID. Record the selected provider and the amount for every attempt. A token identifies payment credentials within a service’s supported use. It isn’t proof that any other processor can use those credentials, and tokenisation doesn’t remove the merchant’s card-data responsibilities.
Stripe illustrates why reporting needs attention. Its multi-processor integration guide uses Payment Records and Payment Attempt Records for externally processed payments. Those payments don’t produce Stripe Balance Transactions because the funds don’t pass through Stripe. A finance process that expects every successful payment to have that balance record will miss the external route.
Retry without creating a second charge
Retry only when the original result and the provider’s rules establish that another attempt is permitted. A confirmed decline says the attempt failed. A timeout says the response didn’t arrive, while the processor might still have accepted the request.
For RET-208, a lost response from Processor A must leave the order awaiting investigation. Immediately sending a fresh payment to Processor B risks a second authorisation or charge. Retrieve the original result or follow the orchestrator’s documented recovery mechanism before creating another attempt.
Duplicate protection must cover the business operation as well as individual network requests. An idempotency key identifies repeated requests for the same operation so the service can avoid performing it twice. Stripe’s idempotency documentation defines that protection within its API. Reusing an identifier at one provider doesn’t establish shared protection at another.
Name the exception owner. For example, the payments lead owns RET-208 until its uncertain attempt is resolved. Support sees “payment confirmation pending” and fulfilment stays blocked. Shopping assistance must use that recorded status before confirming a purchase or offering another payment attempt.
Automatic retries also need explicit limits. Stripe documents cross-processor retry exclusions, including certain authentication outcomes and unsupported features. Spreedly’s Recover documentation maps eligible errors and preserves attempt history. It also warns that a configured second backup can be attempted after any error on the first backup. Don’t assume every stage applies the initial decline filter.
Give one system authority to initiate recovery. If the orchestrator is retrying automatically, a support agent must inspect that attempt history before starting another collection. Record a final successful result once against the order, even when several attempts precede it.
Decide whether the extra layer helps
Choose orchestration when its supported connections solve a named requirement and your team can own the resulting failures and records. Start with your actual merchant countries, settlement currencies and sales channels. Include required wallets or local methods, then test whether each intended route supports them.
Stripe and Spreedly for different workflows
Stripe Orchestration fits a retailer already using Stripe that needs routing to supported external processors. It is in private preview and requires onboarding. Its feature matrix documents processor-specific capture, refund and wallet support. Its overview excludes non-card payments and Terminal, so an in-person channel or local bank-payment requirement needs a separate supported arrangement.
Spreedly fits a retailer building payment flows around a portable vault and several gateway relationships. Its connections directory distinguishes regional availability by connection. Match the actual merchant location and required methods to each gateway instead of treating global coverage as universal eligibility. Composer provides visual routing, while the retailer still integrates the checkout and resulting records.
| Decision | Stripe Orchestration | Spreedly |
|---|---|---|
| Routing and recovery | Dashboard rules select a main and retry processor, subject to feature and authentication limits | Composer branches select gateways; Recover adds configured failover |
| Records and aftercare | Payment and attempt records cover external routes; external processors retain settlement and dispute activity | Tokens and payment history connect gateway attempts; recovery uses the configured gateway references |
| Costs | Third-party processor fees and loss liability remain under those processor agreements; obtain orchestration terms during onboarding | Performance Optimisation pricing requires sales contact; Recover is a paid service requiring production activation |
| Implementation work | Onboard processor connections and adapt reporting for external payment records | Build payment collection, configure gateway connections and connect workflow results to order records |
Stripe’s overview separates orchestration from the external processor’s obligations. Spreedly’s pricing page puts routing in its sales-led Performance Optimisation offering. Compare the written total, including processor charges and implementation, before choosing either route. Neither description establishes a higher approval rate for your store.
Acceptance checks before enabling routing
Test failure handling in the providers’ test environments, with the resulting order and payment records as evidence.
| Test case | Result the retailer must be able to demonstrate |
|---|---|
| Provider fails before accepting payment | A permitted fallback creates a traceable attempt and at most one successful collection |
| Provider accepts payment but its response arrives late | The original attempt is resolved, the order stays on hold until confirmation and no independent second collection starts |
| Successful payment needs a refund | The refund uses the correct original processor reference and its eventual result reaches the order record |
| Payout differs from the captured total | Finance identifies the fees, refunds or missing transactions behind the difference and assigns any unresolved amount |
Use payment reconciliation software to match provider records after payment. Keep routing changes disabled until your payments lead can trace RET-208 from its attempts to the final capture and explain how a refund or payout difference will be resolved.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.