Sandbox and approval
Sign-up is open, so a new account starts in the sandbox. Everything about the integration is real from the first minute: keys, signatures, statuses, callbacks. Only the money is not.
What the sandbox is
A provider named sandbox that accepts every order from an unapproved account and never
touches funds. GET /gw/v1/methods reflects it: it lists what the sandbox can take, which is
every method, every rail, and RUB and USD with no amount bounds. The payment details it
returns are placeholders:
| Rail | Details |
|---|---|
Sbp | phone +70000000000, holder SANDBOX HOLDER, bank Sandbox Bank |
C2c | card 4111 1111 1111 1111, holder SANDBOX HOLDER, bank Sandbox Bank |
Phone | phone +70000000000 |
| none | account SANDBOX-ACCOUNT-0001 |
Driving a sandbox order
The sandbox does nothing on its own: an order stays Created until you act or until it
expires. On the order page in the cabinet, a sandbox order shows two buttons:
- Simulate payment plays a provider confirmation. The order goes straight to
Completed, the credited amount lands on your balance, andorder.completedis delivered to your callback URL through the same worker, with the same signature, as a live order. - Simulate failure plays a provider rejection:
Canceled, andorder.cancelled.
Everything else works as live: expiry after lifetimeMinutes, GET on the order, appeals,
the callback attempt list, Resend callback. Sandbox orders skip the platform's
funds-confirmation step, so they complete immediately; live orders pass through Payed first.
What sandbox orders credit is not real money. It shows on the balance next to live credits but can never be withdrawn: a withdrawal is limited to what live orders brought in.
Driving a test payout
A test cash desk sends its payouts to the sandbox too. They move no money but are
refused, like live ones, beyond your balance. Open the payout on the cabinet's Payouts page
and press Paid out or Failed; the payout.completed or payout.failed callback follows.
Going live
An administrator reviews the account and approves it. From that moment the same cash desks, the same keys and the same callback URLs route to live providers. Nothing changes in your code. The Settings page in the cabinet shows the current mode under Account, and the overview shows a notice while the account is under review.
If the sandbox provider is switched off on the platform, an unapproved account gets
400 MERCHANT_NOT_APPROVED on order creation until it is approved.
Test cash desks
Once the account is approved, its cash desks are live: they route to live providers only and never to a test one. To keep testing after approval, create a separate test cash desk (the Test cash desk switch on the second step of the cash desk wizard). A test cash desk is the mirror image: its orders go to test providers only and never to a live one, so a real payer can never be handed test details, and a test order can never reach real money. The mode is fixed at creation; for the other mode, create another cash desk.
A test cash desk is signed, priced and called back exactly like a live one. Its provider is a
test account at an upstream: it returns test details for every bank it knows
(Alfabank, Vtb, TBank, Sberbank, Ozon, card and SBP, from 100 RUB), and targetBank
on a Monobank cash desk works as live. The outcome follows the amount:
| Amount ends in | What happens |
|---|---|
1 (101, 5001, 15001) | about 20 seconds later the order becomes Completed and order.completed is delivered |
2 (102, 3002) | the order becomes Canceled and order.cancelled is delivered |
| anything else | the order stays Created until it expires |
What a test cash desk credits is test money, as with the sandbox: it shows on the balance and can never be withdrawn.
Limits that can stop traffic once live
- Turnover limits. A cap in USD per cash desk, merchant or the whole platform, per hour,
day or calendar month. When reached, orders answer
TRAFFIC_LIMIT_REACHEDuntil the window rolls over. See Limits. - The appeal guard. A provider with too many open appeals is paused; traffic resumes once they are resolved. This is per provider, not per merchant.
- A stop by the platform. Support can stop a cash desk; it answers
SHOP_STOPPEDwith the reason, and the cash desk card in the cabinet shows the same reason. - Your own switch. A cash desk you disable answers
SHOP_INACTIVE.
GET /gw/v1/methods reports all of these as available: false with a reason.