Environment
There is one environment: production. Here is how to test safely against it.
At launch there is a single live environment. You receive one base URL and one API key at activation, and every call moves real money. There is no separate sandbox, so testing is done against production with small amounts under controlled conditions, then verified end to end before you scale up.
Every call is live. There is no test environment that simulates funds. A payment collects real money and a payout sends real money. Treat every call you make during integration as a real transaction.
How to test against production#
- Agree a short list of test phone numbers and small amounts with your onboarding contact before you start.
- Run one payment end to end: create it, approve it on the test handset, and confirm it reaches success by both webhook and status endpoint.
- Run one payout end to end to a test number, and confirm your wallet
availablebalance moves as expected. - Exercise the failure paths you can trigger safely, such as a customer declining a payment, so your handling of failed and expired is proven.
- Reconcile the test transactions against
/transactionsand/walletsbefore going to volume.
Keep amounts small and recoverable. Use the smallest workable amounts, and where a test moves money to a number you do not control, treat it as a real cost. Your onboarding contact can advise on recoverable test flows.
Going to volume#
Once the flows above are proven and reconciled, you are certified against the go-live checklist and can raise volume. There is no environment switch and no rebind: the base URL and key you tested with are the ones you run in production.
Maly Tech Ltd. This guide is provided for information. Where it differs from your signed agreement, the agreement applies.