Skip to main content

Go live

Going live has two parts: getting your account approved through onboarding and KYB, then switching your integration from test to live keys.

Onboarding and KYB​

Before you can accept payments through the platform, you complete Know Your Business (KYB) verification. This protects you, your customers, and the rails TensorRail runs on. Onboarding has three parts, and collections are not activated until all three are approved:

  1. Business verification (KYB). TensorRail verifies your company, its ownership, and its people.
  2. Risk and compliance review. TensorRail reviews your business model, markets, and customer types against sanctions, anti-money-laundering (AML), and prohibited-use requirements.
  3. Commercial terms. Your corridors, your fee schedule and the rest of your commercial arrangement are agreed with your account manager and set out in your agreement.

What to have ready​

  • Company: certificate of incorporation, constitutional documents, proof of registered address, tax registration, and registers of directors and shareholders.
  • Ownership and control: beneficial ownership information, identification for directors and authorised signatories, and an ownership chart where ownership is layered.
  • Business profile: your business model, website and app, the countries and corridors you want, your customer types and expected volumes, and a source-of-funds explanation.
  • Policies (where applicable): AML/KYC, sanctions, refund and complaint handling, privacy, and fraud-prevention policies.
  • Commercial: the corridors you want activated, and the commercial terms you have agreed.

TensorRail may request more depending on your business, markets, and volumes. A deliberate review here is a feature, not friction: the same gate that verifies you keeps bad actors off the rails your customers pay on.

Your own KYC obligations​

You remain responsible for knowing your own customers. TensorRail runs the rails and verifies you; you verify and monitor the people who pay you. You must maintain KYC and AML controls appropriate to your business, monitor for fraud and abuse, avoid sanctioned parties and prohibited jurisdictions, keep the records your law requires, and cooperate with compliance requests. TensorRail screens against sanctions and financial-crime requirements and may re-verify you periodically.

After approval​

Once approved you receive dashboard access, live API credentials, and your activated corridors and methods. The exact countries and methods activated for your account are shown in your dashboard.

Pre-launch checklist​

Before flipping keys, confirm your integration has the production properties the Quickstart and Testing pages build toward:

  • Secret keys load from environment/secret storage; nothing key-like is in source control or the browser bundle.
  • Every POST /payments and POST /refunds sends an Idempotency-Key (enforcement is live; your retries are only safe if you send the key).
  • Fulfilment keys off the payment_succeeded webhook or a retrieve showing succeeded, never off return_url.
  • The webhook handler verifies TensorRail-Signature over the raw body, de-dupes on event_id, tolerates out-of-order deliveries, and answers 2xx fast.
  • Error handling branches on error.code bands, and distinguishes a request error from a failed payment. See Error intelligence.
  • A failed payment leads to a new payment with a new Idempotency-Key, not a re-confirm.
  • Your order table stores payment_id, and your metadata carries your order reference for reconciliation and exports.

Switch to live keys​

When your integration works end to end on test keys:

  1. Swap the keys. Replace rail_full_test_… with your live secret key rail_full_live_… server-side, and rail_open_test_… with rail_open_live_… in the browser. There is no host change; the key selects the environment. A stray test key in production surfaces immediately as ERR_3051 (mode mismatch) rather than corrupting data. See Authentication.
  2. Re-point the webhook. Set your production webhook URL in the dashboard under Developers → Webhooks, and re-verify a live delivery signature (the signing secret you verify with must be the one for this endpoint configuration).
  3. Watch one real collection. Start with a small real collection on one corridor and watch the whole chain land: confirm returns next_action, the customer completes, the payment_succeeded webhook verifies and fulfils exactly once, the payment shows succeeded on retrieve, and the value appears on your balance. This one transaction exercises every wire your revenue will ride on.

The first days live​

  • Watch webhook deliveries and their attempts in the dashboard; a rising failure count is your earliest signal of an integration or infrastructure issue on your side.
  • Reconcile your balance against your collection export end to end once; after that, your finance process has a verified template. See Money integrity.
  • Keep test keys in your staging environment permanently; every change should replay the test checklist before it reaches live keys.

Keep your profile current​

Tell TensorRail promptly if your ownership or control, directors, legal or regulatory status, products, or markets change, or if any investigation or enforcement action affects you.

Next steps​

You are live and taking real collections. Operate with confidence:

  • Dashboard and account: monitor payments, deliveries, and keys day to day.
  • Money integrity: reconcile settlements against your collection exports.
  • API reference: the endpoint and field reference for the main API — payments, refunds, disputes, customers and the rest. The /v1 account and reporting surface is documented in Reporting API.

TensorRail, Limassol, Cyprus.