Move from staging to production

Staging sign-off

Before requesting production activation, confirm that your integration can:

• obtain and securely cache an API token;
• read the managed test wallet and preserve money as decimal strings;
• create a transfer with a unique idempotency key;
• retry the same transfer without creating a duplicate;
• handle both successful and failed terminal outcomes;
• verify webhook signatures against the untouched raw request body;
• ignore duplicate webhook events using the event ID;
• recover a transfer through the status endpoint; and
• keep secrets and beneficiary account numbers out of logs.

Production setup

Once your MTO is approved for live processing, the CAPSEND MTO platform provides the production credentials and production webhook configuration.

export BASE_URL="https://prod.capsendimto.org/v1"

Do not copy staging credentials or the staging webhook secret into production. Store the new values through your normal production secret-management and deployment process.

Controlled first transfer

1. Confirm the production wallet has sufficient available funds.
2. Use a low, approved amount and validated beneficiary details.
3. Save your idempotency key, external reference, CAPSEND transaction ID, and CAPSEND reference.
4. Confirm the signed webhook is received and processed once.
5. Confirm the status endpoint agrees with the webhook.
6. Reconcile the transfer before increasing volume.

Ongoing operation

• Monitor API errors, webhook failures, and transfers that remain nonterminal longer than your operating threshold.
• Use webhooks for normal updates and status lookup for recovery and reconciliation.
• Rotate exposed credentials immediately through the MTO platform.
• Keep staging checks in your release process without using production beneficiary data.