Skip to content

Go-live checklist

Everything to finish before live keys are issued.

Before live keys are issued

Work through this list with your test key and a reference-rail test run arranged with SmartRemit. When every item is done, ask SmartRemit to take you live; SmartRemit issues your live keys.

WhatsApp

  • Your WhatsApp Business number's credentials are saved in your dashboard.
  • Meta's webhook points at the callback URL on your dashboard's partner page, and the verification succeeded.
  • Your message templates are approved, at minimum transfer_delivered. See WhatsApp setup.

API

  • You hold a test key and call the API from your server only.
  • You created, confirmed and read back a sandbox transaction end to end. See Sandbox.
  • Every POST /transactions sends a fresh Idempotency-Key, and your retries reuse it. See Idempotency.
  • You handle 429 by waiting for Retry-After, and 503 by retrying later. See Rate limits and Errors.

Settlement

  • Your settlement endpoint meets the endpoint rules and is saved with its signing secret.
  • Your endpoint verifies x-smartremit-signature, acknowledges quickly and deduplicates on reference.
  • Your status callbacks are signed with your webhook secret and echo the amount on paid_out.
  • In a reference-rail test run arranged with SmartRemit, you completed the full loop, including the failure path. See Sandbox and Webhooks.

Compliance

  • Your KYC mode is agreed, and you send sender.kyc_status and sender.name on every transaction. See KYC delegation.

Live money on your own rail

Going live with your own settlement rail needs a second SmartRemit approval after go-live. SmartRemit approves your workspace for live money on your rail when:

  • your compliance setup is signed on the Onboarding page of your workspace (signing it turns on verify before send for your customers);
  • two of your team are named as compliance users, each with two-step verification;
  • your own WhatsApp Business number is connected;
  • your agreement with SmartRemit is on file;
  • the further checks SmartRemit adds are met (your Controls page lists every check and its state).

When SmartRemit turns on live money for your rail, AML holds before payout are switched on for each of your corridors that has no setting yet, except India (IN), with all three rules: structuring, a large first transfer, and a large transfer to a new recipient. A corridor SmartRemit adds to your account later gets the same default when it is added. Corridor rules, these holds included, do not apply to transfers sent from India. A held transfer waits for review before payout. Your admins can change the rules for each corridor on the Settings page; each change asks for two-step verification.

Until then, live transactions on your rail are refused with 403 and code partner_not_live. Sandbox transactions are not affected. After the approval, a live Partner API transaction with a USDC payout is refused with 403 and code capability_off until that feature is approved. Business payments, repeat payments and AI apps stay closed in the chat, the portal, the pay pages and AI apps until they are approved, and customers see a neutral message there. SmartRemit reviews each feature first; your admin then approves it on the Controls page. See Errors.

Your switches

Your admins can pause your own workspace on the Controls page: new sends and settlement (for every corridor or for one), the AI agent and AI agent tools. A pause takes effect within about 15 seconds and stays until your team resumes it. Resuming asks the admin to confirm their identity again. SmartRemit sees each change, and your workspace shows a notice while a pause is on.