Every storefront stack ships with its own money pipes — Shopify Payments, Woo gateways, Wix payments, PayPal buttons — and each one has different underwriting, reserve behavior, and payout timing. Gateway-by-gateway mechanics and how merchant cashout works across the platform economy: full map hidden below.
— RELATED GUIDES —
Store honest, category declared, disputes refunded below threshold — the platform economy pays out to storefronts that behave like storefronts. Tracking numbers, policy pages, matched banks; the gateway reviewer sees a business because that's what you built it to look like, functionality included.
STACK MAP (PLAIN VERSION)
A storefront (Shopify/Woo/Wix-class) plus a payment gateway (Stripe underneath Shopify Payments in many regions, PayPal Commerce, Adyen-class processors, direct Stripe on Woo via plugin) turns storefront orders into settled funds. The gateway handles underwriting and payouts; the storefront platform just renders checkout. Merchant cashout = storefront business receiving through gateway, gateway paying out to bank — same shape as Stripe guide, different branding and quirks per platform.
GATEWAY-BY-GATEWAY
UNDERWRITING REALITY
THE CASHOUT SHAPE
DEATH CONDITIONS
WORKING SEQUENCE
Legitimate-looking store, honest onboarding, disputes refunded cheaper than fought — platform cashout is retail business done with compliance awareness. Every gateway wants the same customer: boring store, steady volume, tracking numbers on file.
A storefront (Shopify/Woo/Wix-class) plus a payment gateway (Stripe underneath Shopify Payments in many regions, PayPal Commerce, Adyen-class processors, direct Stripe on Woo via plugin) turns storefront orders into settled funds. The gateway handles underwriting and payouts; the storefront platform just renders checkout. Merchant cashout = storefront business receiving through gateway, gateway paying out to bank — same shape as Stripe guide, different branding and quirks per platform.
GATEWAY-BY-GATEWAY
| Stack | Processor underneath | Payout behavior | Quirks |
| Shopify Payments | Stripe/Adyen-class by region | T+2-ish standard, faster at tenure | Shopify's own risk layer + processor underwriting stacked |
| Shopify + PayPal button | PayPal | PayPal balance → bank | dispute regimes split across two systems |
| WooCommerce + Stripe plugin | direct Stripe | Stripe schedule | you ARE the merchant-of-record stack owner — full config control |
| Wix Payments | Wix's own licensed processing | rolling schedule | platform-coupled, less portable |
| BigCommerce/multi-gateway | varies | per gateway | split settlement across processors complicates story |
UNDERWRITING REALITY
- Every gateway scores storefront: domain age, traffic patterns, product category, refund policy, fulfillment proof (tracking numbers), contact info quality.
- High-risk categories (digital goods, supplements, gambling-adjacent, dropship-class): longer review, reserves 5-15%, higher fees or decline.
- Chargeback ratio is THE metric: above category thresholds → reserve hikes, payout holds, termination — VISA/MC monitoring programs cascade across gateways (terminated once, scrutinized everywhere via industry databases).
- Storefront legitimacy signals matter: real About page, working support email, consistent branding, plausible product catalog — gateway reviewers literally browse your store.
- Payout account must match merchant KYC — third-party bank details = instant hold.
THE CASHOUT SHAPE
Bash:
storefront: real-looking catalog + policies + support channel
-> gateway: honest category at onboarding, matched bank, entity if volume demands
-> orders: fulfilled with tracking where physical, instant-delivery where digital (refund policy visible)
-> disputes: refund fast under $X (dispute-avoidance math), contest with evidence only when winnable
-> payouts: standard schedule, no premature drains, reserves budgeted
-> growth: volume ramps WITH account tenure, seasonality plausible for categoryDEATH CONDITIONS
- Ghost store: orders without fulfillment proof — chargebacks come en masse, gateway freezes, entity flagged in industry databases.
- Volume spikes unexplained by marketing: $500/day store jumps to $10k overnight = classic fraud-store pattern for reviewers.
- Refund-policy violations: buyers who can't get refunds file disputes; dispute ratio kills accounts faster than fraud flags sometimes.
- Multi-gateway same-story splitting: same entity spreading volume across processors to dodge thresholds — industry data links entities.
- Third-party payments into gateway-connected bank: mule-graph at the receiving bank, gateway balance misused.
- Chargeback monitoring program enrollment: once in VISA/MC monitoring, EVERY future gateway onboarding asks about it — disclosure required, history follows.
WORKING SEQUENCE
Bash:
storefront build: plausible business from day one (catalog, policy, contact)
-> gateway: single primary gateway first, honest category
-> fulfill: tracking numbers on every physical order, instant delivery + evidence on digital
-> disputes: proactive refunds below dispute cost, evidence packets when contesting
-> payout: standard schedule to matched bank, reserves in cashflow plan
-> expand: second gateway only after first shows clean 60-90 day historyLegitimate-looking store, honest onboarding, disputes refunded cheaper than fought — platform cashout is retail business done with compliance awareness. Every gateway wants the same customer: boring store, steady volume, tracking numbers on file.
— RELATED GUIDES —
- Stripe Cashout Method: Merchant Account Payouts
- PayPal Cashout Method 2026: From Balance to Bank Clean
- eBay Cashout Method: Selling and Payouts
- Bank Drop Setup: Opening and Running Drops 2026
- Cashout Methods for Clean Money 2026: The Complete Guide
Store honest, category declared, disputes refunded below threshold — the platform economy pays out to storefronts that behave like storefronts. Tracking numbers, policy pages, matched banks; the gateway reviewer sees a business because that's what you built it to look like, functionality included.
Last edited: