Money leaves
through the right hands.
Approval flow for merchant balance withdrawal and movement requests. Operators review, approve or reject requests with the right role - every action audit-logged.
Money movement deserves a workflow, not a free-for-all
Merchants ask for early payouts, balance transfers, currency conversions. Each request needs review, approval and an audit trail. Balance Requests turn that into a clean workflow.
Approval workflow
A payout request moves through a defined path rather than straight out of the door. It is raised, checked against the limits that apply to that account and currency, and approved by someone with the authority to approve it, with every step attributed.
Role-based
Sensitive requests require approval from a user with the right role. Threshold-based - small requests auto-approve; larger requests escalate.
AML-scored
Every request scored against your AML rules. Auto-approve low-risk, queue for review, or block. Suspicious patterns trigger alerts.
Branded merchant flow
Merchants submit requests through the merchant control panel - branded as your platform, integrated into the same balance view.
Full audit log
Every request, approval, rejection and modification logged with user, timestamp and reason. Searchable and exportable.
How requests flow
- Submit
Merchant submits request through the merchant control panel. Required fields and supporting documents per request type.
- Score
AML rules score the request. Low-risk auto-approves; higher-risk queues for review.
- Approve
Operator reviews and approves with the right role. Funds move; merchant notified; full audit log captured.
Frequently asked questions
Can I auto-approve below a threshold?
Yes. Requests below a threshold you set can clear automatically while anything above it waits for a person, which keeps small routine payouts moving without giving up control of the large ones.
How does AML scoring work?
Every request scored against your AML rules. Define thresholds; the platform auto-approves, queues or blocks accordingly.
Can a merchant track its own requests?
Yes. The merchant sees the state of their own requests in their portal, which removes the most common support question about a payout without exposing anything belonging to another merchant.
How are large requests escalated?
Threshold-based escalation. Large requests can require multi-level approval - first reviewer plus a second approver.
Are rejections explained to the merchant?
Yes. Operators add a reason on rejection; the merchant sees the reason in the merchant control panel.
Where is data hosted?
Hosting, retention and data residency are set per deployment rather than fixed, and each brand is served from its own domain. Tell our team what your regulator and your customers require and we will confirm the arrangement in writing.