How it works
The platform is designed around operational clarity.
Owners sign in once per tenant, sync Yandex drivers, enable or disable work conditions for payouts, and monitor every request through transaction and intervention views.
The first release is built around real Yandex data, tenant isolation, work-condition gating, intervention visibility, and direct bank submission wiring.
Drivers, transactions, work-condition payout gating, interventions, and integration settings.
SMS entry, live balance, one active payout at a time, and a full payout trail.
Domestic transfer submission is wired against the BOG test path, with failures routed into interventions.
Admin lives on admin.neopay.cloud. Drivers stay on tenant subdomains like tenant.neopay.cloud.
Owners sign in once per tenant, sync Yandex drivers, enable or disable work conditions for payouts, and monitor every request through transaction and intervention views.
Drivers enter via their tenant subdomain, verify by SMS, see the latest trusted balance, and request a payout only when the balance is fresh and their current work condition is allowed.