Pay-Outs & Withdrawals

Pay-Outs (Sending Funds)

Pay-outs describe how funds leave 3PAY, either through manual actions in the dashboard or automated withdrawal mechanisms.

This guide applies to merchant balances and explains the different payout models supported by 3PAY.

---

Overview of payout types

3PAY supports the following payout methods:

1. Manual payouts (Dashboard)
2. Withdrawal requests (API)
3. Auto-withdrawals (transaction-based)
4. Auto-payouts (balance-based)

Each method serves a different operational use case.

---

1️⃣ Manual payouts (Dashboard)

Manual payouts are initiated directly by the merchant through the 3PAY dashboard.

How it works:

• Merchant selects a withdrawal amount
• Merchant provides a destination wallet address
• Transaction is reviewed and processed
• Funds are sent on-chain to the specified wallet or to FIAT providers

Best for:

• Low-frequency withdrawals
• Operational control
• Treasury management
• Early-stage merchants
• Off-ramp solutions

Manual payouts provide maximum control but require manual action.

---

2️⃣ Withdrawal requests (API)

Withdrawal requests allow merchants to programmatically request withdrawals via API.

How it works:

• A withdrawal request is created through the API

• The request includes:

  • Amount
  • Asset & network
  • Destination wallet

• The request is processed according to merchant permissions and rules

Best for:

• Platforms and fintech applications
• Automated withdrawal workflows
• User-initiated withdrawals

Withdrawal requests may still be subject to:

• Review rules
• Thresholds
• Compliance checks

---

3️⃣ Auto-withdrawals (transaction-based)

Auto-withdrawals are designed for end-user withdrawal flows, where withdrawals are processed automatically per transaction, based on predefined rules.

How auto-withdrawals work

• An end user requests a withdrawal (e.g. from a trading platform)

• If the withdrawal amount meets the auto-withdrawal criteria:

  • The withdrawal is processed automatically
  • Funds are sent to the specified third-party wallet

• If the amount exceeds the threshold:

  • The withdrawal may require manual review

Example

A forex trading platform configures auto-withdrawals as follows:

• Withdrawals under $500 USDT → processed automatically
• Withdrawals above $500 USDT → manual approval required

Each auto-withdrawal can:

• Use a different destination wallet
• Be evaluated per transaction

Best for:

• Trading platforms
• High-volume user withdrawals
• Reducing operational overhead

---

4️⃣ Auto-payouts (balance-based)

Auto-payouts are designed for merchant treasury automation, not end-user withdrawals.

How auto-payouts work

• Merchant defines a fixed payout wallet

• Merchant defines a balance threshold

• When the merchant’s 3PAY balance reaches the threshold:

  • A payout is automatically triggered
  • Funds are sent to the predefined wallet

Example

• Auto-payout threshold: $10,000 USDT

• Destination wallet: Merchant treasury wallet

• Once balance ≥ $10,000:

  • 3PAY automatically sends funds to the treasury wallet

Auto-payouts:

• Always use a fixed destination wallet
• Are balance-based, not transaction-based

Best for:

• Treasury management
• Liquidity consolidation
• Automated settlement to external payment providers

---

Comparison of payout types

---

Fees & processing

• Network fees apply to all on-chain payouts

• Fees are displayed before execution

• Processing time depends on:

  • Network conditions
  • Asset type
  • Payout configuration

---

Sandbox vs live behavior

• Sandbox payouts use testnets only
• No real funds are moved in sandbox
• Auto-withdrawal and auto-payout logic can be tested safely
• Sandbox configurations do not carry over to live

---

API reference links

Use the API Reference for implementation details.

Place the following links here using ReadMe’s API Reference linking feature:

• 🔗 Create Withdrawal Request → POST /withdrawals
• 🔗 Get Withdrawal Status → GET /withdrawals/{id}
• 🔗 Auto-Withdrawal Rules → relevant configuration endpoint
• 🔗 Auto-Payout Configuration → relevant configuration endpoint

This keeps payout logic centralized and avoids duplication.

---

Important notes

• All payouts are irreversible once broadcasted
• Thresholds and rules should be tested in sandbox
• Destination wallets must be validated carefully
• Large payouts may be subject to additional review