Supported Orchestration featuresVersion bêta privée
Learn about the features that Orchestration supports.
Want access to Orchestration?
Orchestration is in private preview. Share your email address to request access.
When using Orchestration with different payment processors, you might encounter payment features that don’t work that you would normally expect to work with Stripe. In these cases, the request fails with a 400 error code orchestration_. The first unsupported feature found is also included in the error message.
Error protection
During the onboarding process, you can opt into error protection, which automatically handles these cases. If we see a payment requesting an unsupported feature, we route the payment to Stripe instead of the originally determined payment processor. This avoids returning these validation errors. We also consider error protection during cross-processor retries. However, if there was a failover and the original processor was Stripe, we ignore the error protection configuration. We do so to avoid a duplicate attempt on Stripe. Contact your Stripe representative to enable this configuration.
Supported features
These are the features currently supported for the other payment processors through Orchestration.
| ADYEN | BRAINTREE | WORLDPAY | |
|---|---|---|---|
| Automatic confirmation | |||
| Automatic capture | |||
| Manual capture1 | |||
| Full refunds | |||
| Partial refunds | |||
| 3DS | |||
| Statement descriptors2 | |||
| Wallets (Apple Pay, Android Pay, Google Pay)3 | |||
| Network tokens | |||
| Recurring transactions |
1 Multicapture is currently not supported.
2 statement_ isn’t supported on any payment service provider. statement_ is only supported on Adyen.
3 3DS isn’t supported with Apple Pay and Android Pay.
If you’re interested in a feature that Orchestration doesn’t currently support, contact your Stripe representative.