Page body
What this module is for
Automatic Withdrawal lets operators maintain the rule set that decides which withdrawals can be auto-processed and then monitor how those rules behave in production.
This route family has three distinct operator jobs:
- maintain the rule register itself
- create or edit one rule and its qualification criteria
- review processed history and handle withdrawals that did not qualify automatically
Surface map
List: rule table with search, status filter, create, edit, activate, deactivate, and delete actionsForm: create and edit flow for one automatic-withdrawal ruleDetail: management workspace anchored by theRules,History, andNon-Qualified Withdrawalstabs
Common operator questions
- which rule is currently active and what priority it has
- whether a rule is global or effectively personal to one customer
- how daily limit, KYC, NGR thresholds, countries, methods, and tags interact
- why a withdrawal was processed, rejected, or left in the non-qualified queue
- whether a pending withdrawal can be processed one by one or in bulk
Verification status
- status:
verified_backend - FE source:
nx-admin-fe-workspace - backend source:
gs-admin-backend nx-workspace: not required for current operator wording