3D Secure
3D Secure authentication where your provider supports it: the customer completes it on the page the provider hosts and returns to your site.
Read the docs Payment Orchestration
Bring the providers you already use.
Connect your own provider accounts and run them through one integration: one API and one set of webhooks over every provider connected to your account.
What Payment Orchestration does
01Your providers
One integration over your own provider accounts.
Keep your own accounts with the providers you already use, and connect them to your TensorRail account. Your integration talks to TensorRail only, whichever provider takes the payment.
✓Provider accounts connected in your dashboard
your integrationconnect
provider Ayour account
provider Byour account
integrationPOST /payments
webhooksone set, signed
one API · one set of webhooks
02Routing and error intelligence
Every payment follows the routing set up for your account.
Payments are routed across the rails enabled for your account by the routing set up for it, and every decline comes back as one unified error code with retry guidance. The code says whether a new attempt is worth making, so retries are targeted, not blind.
✓Rule-based routing · 170+ unified error codes
rule-based routingyour providers
rule · market · method · currency · priority
payment 1provider Aapprovedrule match
payment 2provider Adeclined · issuer_unavailableretriable
one unified error code · retry guidance per code
03Card fields
Card fields hosted by the card processor.
Card details are entered in card fields hosted by the card processor, so card data never touches your servers. What you receive is a token you can charge and save for returning customers, on the card processor that issued it.
✓Card fields hosted by the card processor · a token back
card fieldshosted by the card processor
checkout page
card fields
4242 4242 4242 424212/28 · •••
returnstok_9dW1
your servers see a token · not the card number
04Saved methods and mandates
Save a method once, with your provider.
Save a customer's method or mandate with your provider on the first payment, and charge it again for renewals and returning customers without re-entry. A saved token works with the provider that issued it.
✓Methods and mandates saved with your provider
saved methodswith your provider
first paysetup_future_usagesaved · pm_9c1f
renewaloff_session · pm_9c1fcharged
the token works with the provider that issued it
The card lifecycle
Authentication, capture and disputes.
Capture and cancel
Authorize now and capture later, in full or in part, or cancel the authorization, where your provider supports it.
Read the docs Disputes
Disputes where your provider reports them, with each step of the dispute sent to you as a webhook event.
Read the docs How you use it
Hosted Checkout and Payment Links work where your provider supports them; the REST API works with every provider connected to your account.
Bring your stack. Keep one integration.
Tell us which providers you use and where you sell, and we will set up your account around them.