Private preview
Route off-session payments with Orchestration Private preview
Use Stripe Orchestration to route off-session payments across supported processors.
Use Orchestration with the Off-Session Payments API to route an off-session payment across supported processors. Enable Orchestration on each off-session payment request, then use your active Orchestration rules to select the processor.
Warning
Smart Retries is incompatible with Stripe Orchestration.
Orchestration with the Off-Session Payments API only supports card payments and doesn’t support Connect or requests that contain raw card data.
Before you begin
- Get access to the Off-Session Payments and Stripe Orchestration private previews.
- Onboard your destination processor .
- Create and activate an Orchestration routing configuration .
Configure routing rules Dashboard
In a sandbox, create and activate routing rules in the Dashboard. Rules can evaluate supported payment attributes, such as amount, currency, metadata, and card properties. Each rule can select the main processor and an optional retry processor.
Create an off-session payment Server-side
Create an OffSessionPayment and enable Orchestration for the request.
Command Line
Select a language
cURL
Stripe CLI
Ruby
Python
PHP
Java
Node.js
Go
.NET
No results
The payments_orchestration.enabled parameter opts this off-session payment into your active routing configuration. Don’t pass a processor ID or routing-rule ID in the request.
Verify routing
Use sandbox rules and test payment methods to create an off-session payment. Confirm that the payment matched the intended rule and processor. Review Orchestration feature support for processor-specific limitations.
