Pay-Ins (Accepting Funds)

Pay-Ins

Pay-ins describe how funds enter 3PAY, how they are detected on-chain, and how they become available in merchant or user balances.

This guide applies to all payment methods supported by 3PAY, including:

• Invoice payments
• Wallet payments

Supported assets & networks

3PAY currently supports stablecoin pay-ins on the following networks:

ℹ️

Network availability may differ between sandbox and live environments.

How pay-ins work

When a payment is sent to a 3PAY address, the following steps occur:

1. Transaction broadcasted The sender submits a transaction on the selected blockchain network.

2. On-chain detection 3PAY monitors the blockchain and detects the incoming transaction.

3. Confirmation threshold reached Once the required confirmations are met, the transaction is considered settled.

4. Balance credited Funds become available in the merchant wallet balance.

Address behavior

Pay-ins may be sent to different address types depending on the payment method.

Invoice addresses

• Generated per invoice
• Used for one-time payments
• Linked to a single transaction

User wallet addresses

• Assigned per user
• Persistent across deposits
• Used for account-based balances

Addresses are network-specific and must be used correctly.

Network mismatches & incorrect payments

Sending funds on the wrong network or using an unsupported asset may result in:

• Delayed detection
• Manual review
• In some cases, irrecoverable funds

Examples:

• Sending ERC20 USDT to a TRC20 address
• Sending non-supported tokens

⚠️

Always ensure the correct network and asset are selected before sending funds.

Confirmation times & network behavior

Confirmation times depend on:

• Network congestion
• Blockchain performance
• Testnet vs mainnet conditions

Sandbox environments (Sepolia, Nile) may experience slower or unstable confirmations.

Sandbox vs live behavior

Sandbox balances and transactions cannot be transferred to live.

Webhooks & notifications

3PAY sends webhook events for pay-ins, including:

• Transaction detected
• Payment confirmed
• Balance updated

Webhook timing depends on confirmation status.

Webhook endpoints must be configured separately for sandbox and live.

Important notes

• Pay-ins are irreversible once confirmed
• Confirmation thresholds are enforced for safety
• Network fees are paid by the sender
• Address reuse rules depend on payment method

Summary

Pay-ins define how money enters 3PAY, from on-chain detection to balance availability.

Understanding pay-in behavior ensures:

• Accurate reconciliation
• Proper user experience
• Predictable settlement