Production Readiness

1. Account & compliance readiness

Before going live, ensure:

☐ Business profile fully completed ☐ Merchant verification (KYC / KYB) approved ☐ Approved business activity and jurisdiction ☐ Authorized users assigned correct roles

Live transactions are not permitted without completed verification.

2. Environment separation confirmed

Confirm you are operating in the correct environment:

Sandbox dashboard: https://sandbox.3pa-y.com/
Live dashboard: https://dashboard.3pa-y.com

☐ Live API keys generated from the live dashboard ☐ Sandbox keys are no longer used in production ☐ Environment variables clearly separated

Never reuse sandbox credentials in live systems.

3. Payment flow validation

Ensure the payment flow(s) you use have been fully tested in sandbox.

Invoice payments

☐ Invoices created successfully ☐ Payment instructions displayed correctly ☐ Status transitions handled correctly ☐ Webhooks processed reliably ☐ Late or wrong-invoice scenarios understood

Per-user wallets

☐ Users created successfully ☐ Wallet addresses retrieved correctly ☐ Deposits confirmed and reflected in balances ☐ Wallet balances used safely inside your product

Only Successful transactions should trigger product actions.

4. Webhooks & reliability

Webhooks must be production-ready.

☐ Live webhook endpoint configured ☐ Signature verification implemented (if supported) ☐ Idempotent processing (duplicate events handled) ☐ Events stored for audit and debugging ☐ Graceful retry handling implemented

Webhook failures are the most common production issue.

5. Network & user safety controls

☐ ERC20 vs TRC20 network clearly displayed to users ☐ UI warnings for irreversible blockchain transactions ☐ Validation for destination addresses (where applicable) ☐ Wrong-network scenarios handled gracefully

3PAY is not liable for user input errors. Your UI must make risks clear.

6. Payout & withdrawal safeguards

If using withdrawals, auto-withdrawals, or auto-payouts:

☐ Manual payouts reviewed and tested ☐ Auto-withdrawal thresholds correctly configured ☐ Auto-payout destination wallet verified ☐ Large payout review processes understood ☐ Destination wallets double-checked

Once broadcasted, payouts cannot be reversed.

7. Security hardening

Before going live:

☐ API keys stored securely (server-side only) ☐ 2FA enabled for dashboard users ☐ Dashboard access limited to trusted personnel ☐ Access revocation process in place

Security misconfiguration is a major risk at scale.

8. Reconciliation & monitoring

Ensure your team can reconcile and monitor activity:

☐ Transaction hashes accessible from dashboard ☐ Internal records match 3PAY transaction history ☐ Monitoring in place for failed or delayed transactions ☐ Support escalation path defined

Reconciliation should rely only on Successful transactions.

9. Legal & responsibility clarity

Before enabling production:

☐ Refund and reversal limitations understood ☐ Non-liability for wrong wallet address/network accepted ☐ Merchant terms reviewed ☐ End-user disclosures implemented in your UI

Clear responsibility boundaries prevent disputes.

10. Final go-live confirmation

☐ All sandbox tests completed ☐ All production settings verified ☐ Internal approval granted ☐ Stakeholders informed

Once live payments are enabled, transactions are real and irreversible.