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. Done in this order, nothing has to be redone.

The order, step by step​

  1. Accept your invitation. Your account manager opens your account and you receive an email invitation to the dashboard. Set your password and turn on two-factor authentication. Sign in through that invitation rather than creating a separate account: the methods and pricing agreed with your account manager are set up on the account opened for you. Your dashboard, and the test keys and KYB form in it, open once your account manager approves sandbox access for the account; until then signing in shows that the account is pending approval.
  2. Build on test keys. Take your test keys from Developers → API Keys and build the whole integration against them: create, present, confirm and the webhook. See the Quickstart and Testing and sandbox.
  3. Submit KYB from the dashboard, with your beneficial owners. See Onboarding and KYB for what to have ready.
  4. Your methods are enabled and priced. Once KYB is approved, your account manager enables the methods in your agreement and sets their pricing on your account, before your first live payment. The methods enabled for you are then shown in your dashboard.
  5. Create live keys under Developers → API Keys. Creating a live secret key asks for your two-factor code.
  6. Swap the keys on the same base URL. Nothing else in your integration changes. See Switch to live keys.
  7. Point your webhook endpoint at production and verify a live delivery. Your account has one endpoint for test and live events, so test events reach production too: see Switch 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 our prohibited-use policy and our partners' acceptance criteria, and asks you for evidence of your own sanctions and anti-money-laundering controls.
  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, including producing evidence of those controls when we ask for it. TensorRail does not run sanctions or financial-crime screening on your behalf, and nothing on this platform should be relied on as that screening; we may ask you to re-verify periodically.

Compliance certificates​

Some of the review above asks you for evidence: proof of your own sanctions and AML screening, a licence, an audit letter. Once your account is live, manage those records from the dashboard, under Risk & Compliance → Compliance Documents: see what is on file, with each certificate's status and expiry, and register a new or renewed one with Register certificate. A banner at the top of the same page flags any certificate expiring within 30 days or already expired. There is no API call for any of this.

These are a record of the evidence you provide, not a screening service: submitting a certificate does not cause TensorRail to screen anything on your behalf, and nothing here replaces the controls you are required to run yourself.

After approval​

Once approved, the methods in your agreement are enabled and priced on your account, and you can create live API keys from the dashboard you have been using since your invitation. The exact countries and methods activated for your account are shown in your dashboard. Taking UPI? Read the UPI rules before your first live payment.

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 /v1/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. Create your live secret key under Developers → API Keys (it asks for your two-factor code), then replace rail_full_test_… with it (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. Point the webhook at production. 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). There is one endpoint for test and live, so from now on test-mode events arrive there as well. A payment event's object carries livemode, false for a test payment: check it first, and keep test events out of fulfilment.
  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. Staging's webhook events are delivered to your one endpoint, where the livemode check keeps them out of fulfilment.

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.