Collections and payouts, one clean control layer.
AquaPay keeps merchant checkout, payout operations, user processing, and admin approvals inside one single-sign-on system with role-based redirects to the right dashboard.
Built for payment teams that need clarity, not clutter.
The platform separates customer payments, merchant tools, payout operations, and internal approvals without forcing everyone into the same dashboard.
Collections
Hosted checkout, payment links, callbacks, and order visibility in one merchant flow.
- `/api/payments` for pay-ins
- PayU webhook handling
- Merchant order tracking
Payouts
A dedicated payout workspace for merchants and operators, isolated from pay-in routes.
- `/api/payouts` for payouts
- YYPay webhook isolation
- Payout queue monitoring
Single Sign-On
Admins, merchants, and payout users all use the same sign-in page and land on the right surface automatically.
- One login page
- Role-based redirect
- Shared session across subdomains
Simple routes, clear separation.
Pay-in routes stay under ` /api/payments ` and ` /api/webhooks/payu `. Payout routes stay isolated under ` /api/payouts ` and ` /api/webhooks/yypay `.
Fast integration, fewer surprises.
Start with the shared login flow, wire your pay-in or payout endpoints, and keep each role on its own surface.
POST /api/payments
POST /api/webhooks/payu
POST /api/payouts
POST /api/webhooks/yypay
Login once -> redirect by role
Need onboarding or deployment help?
Use the shared sign-in flow for daily operations, then keep merchant, user, and admin work on their own dashboards.