Modes: Automatic vs Manual

Manual Withdrawals

Definition. A withdrawal executes only after approval according to your configured thresholds and roles.

Key points

• Approval required: Requests remain pending_review until an authorized approver approves.
• Thresholds: Define limits (e.g., amounts ≥ X require approval; amounts < X may be auto-eligible).
• Default: If automatic mode is not enabled in the dashboard, all withdrawals stay manual to minimize risk.
• Use cases: Large-value movements, sensitive destinations, first-time destinations, exception handling.

Operational notes

• Maintain an approval log (who, when, policy version, comments).
• Require approval for new destination addresses/corridors and high-value requests.
• Set internal SLAs for approvers to keep service levels predictable.

Automatic Withdrawals

Definition. A withdrawal executes immediately if the request passes balance and policy checks—no human approval.

Key points

• Opt-in: Must be explicitly enabled per merchant in the dashboard.
• Auto-thresholds: Configure limits that reflect your risk profile (e.g., per-transaction cap, daily cap, velocity limits).
• Destination validation: Requests fail if the destination wallet address is invalid or fails format/network checks.

Insufficient funds behavior (choose one)

• Soft fallback: Route the request to Manual review automatically.
• Hard fail: Reject the request with a terminal failure status.

Use cases

• High-frequency, low-value withdrawals where speed is critical.
• Mature operations with monitoring and clearly defined caps.

Configuration Model (at a glance)

• Enablement: Manual is the safe default; Automatic must be turned on explicitly.
• Limits: Per-transaction, daily, and rolling-period caps; velocity controls.
• Routing: Requests exceeding limits automatically route to Manual.
• Destination checks: Enforce network/format validation for wallet addresses; reject on mismatch.

Recommended Baselines

• When enabling automatic, start with low per-transaction caps and a daily limit, using soft fallback to Manual.

Comparison

Compliance Notes

• 3PAY provides the infrastructure and controls; you configure thresholds and approvals to match your risk and licensing.
• Apply sanctions/AML screening to outbound movements and retain evidence of checks.
• Ensure destination choices (corridors, banks, PSPs, external wallets) align with your internal policies and jurisdictional requirements.