One platform, any market
TensorRail is a single payment platform. You integrate once and accept payments across many methods and markets. Same API, same account, same balance, same webhooks, same error contract, everywhere you operate. There is no second product to adopt and no second integration to learn.
What you get
- One integration, many markets. Accept the local payment methods your customers already use across regions, from a single API, with no per-country integration, no local entity of your own, and no local bank account to open. The methods and markets open to your own account are shown in your dashboard; the unauthenticated
GET /v1/capabilitiescatalogue lists what the platform covers overall. As our reach grows, your account manager can walk you through what we can open for you next. - One acceptance surface. You accept each payment on the local rail the customer expects, and the collected value is recorded to your balance for that currency. You see every step: the payment, the fees booked against it, and the ledger postings underneath.
- One error contract, whatever the rail. Every failure arrives as a stable
ERR_NNNNcode with the same meaning across every processor we route to, so you write your handling once and never reconcile one processor's decline vocabulary against another's. Approval-optimised routing and cross-processor decline recovery are built and are enabled per account; check with your account manager whether they are switched on for you, and do not build against them until they are.
One contract, held everywhere
The claim "one platform" is checkable, because the same small contract is what you touch in every market and on every integration path:
| Surface | The one contract |
|---|---|
| API | https://api.tensorrail.com; create, confirm, retrieve, capture, cancel, refund |
| Payment object | One curated field set; status is the only thing you branch on |
| Statuses | requires_payment_method through succeeded / failed / cancelled, identical on every rail |
| Errors | One ERR_NNNN catalog; a decline means the same thing in every market |
| Webhooks | One signed event contract (TensorRail-Signature), one verification recipe |
| Money | One balance per currency, one double-entry ledger, one set of exports |
| Keys | rail_full_… server-side, rail_open_… browser-side; the key selects test or live |
Expanding to a new market changes none of these. That is the operational meaning of "you never re-integrate".
Why it holds up
For a team betting its revenue path on a platform, the reasons to trust it should be specific:
- The balance is provable. Every credit is a posting on a double-entry ledger, an automated reconciliation checks balance against ledger every hour, and you can export the underlying collections and re-derive the number yourself. See Money integrity.
- Duplicates are prevented, not cleaned up. Idempotency is enforced on payment and refund creation, so a network retry or a double-submitted checkout cannot collect twice. See Orchestration and routing.
- Failures are one language. Declines and errors resolve to one stable catalog with retry semantics, instead of a per-rail dialect your team has to maintain. See Error intelligence.
- The response surface is deliberately curated. The payment, refund, and dispute objects expose a stable allowlisted field set, so the contract you code against does not shift underneath you, and internal routing detail never leaks into it.
- Operations are self-serve. Key rotation, webhook endpoint and signing-secret management, delivery inspection and re-drive, exports, and step-up verification on sensitive actions (like rotating an API key) are all first-class in the dashboard, not support tickets.
How to think about it
TensorRail is the technology platform that connects you to payment acceptance across markets, and runs the routing, reconciliation and reporting on top. You contract only with TensorRail and integrate only with TensorRail, so you do not assemble it market by market: the local connectivity is already there, and adding a market is account configuration rather than a new integration.
Your balance is what the ledger says you have collected, one figure per currency, derived from the postings under it rather than stored beside them. See Money integrity for how it is backed and checked.
One integration, everywhere
Because it is one platform, the Quickstart, the payment lifecycle in How it works, the error catalog, and webhooks apply unchanged across every market and method. There is nothing new to learn as you expand.
TensorRail, Limassol, Cyprus.