At a glance
Revenue split by payment gateway / processor (Stripe, PayPal, BigCommerce Payments, Cybersource, Adyen, Square, etc). Materially more important on BigCommerce than on Shopify because BC supports 70+ external gateways alongside its own BigCommerce Payments offering, the gateway split can be the single most consequential financial decision the merchant makes.
| What it counts | SUM(totalIncTax) per paymentMethod value over the last 30 days, with each order attributed to whichever gateway processed its payment. |
| VAT / tax treatment | Tax-inclusive (uses totalIncTax). |
| Shipping | Included (part of totalIncTax). |
| Discounts | Already deducted (post-discount customer-billed total). |
| Refunds | Not deducted (gross gateway-attributed revenue). To get refund-net per gateway, subtract gateway-side refund volume from the gateway dashboard. |
| Cancelled / voided orders | Included if the order’s payment status reached captured; excluded if it was declined or voided. The boundary depends on BC’s status transition timing. |
| Currency | Multi-currency arithmetic without FX. A multi-gateway, multi-currency BC store sees an aggregated mix; for cleaner gateway accounting use a per-currency view. |
| Channels / sources | All BC channels contribute. Channel-specific patterns: web orders typically use Stripe / BigCommerce Payments; POS uses Square or BigCommerce POS Payments; marketplace orders use marketplace-side processors (Amazon Pay, eBay Managed Payments) which may show as a single aggregated value. |
| Why this matters more on BC than Shopify | Shopify Payments is the dominant choice on Shopify (~70% of stores, partly because Shopify discounts processing fees for using their gateway). BC has BigCommerce Payments but does not penalise external gateways; merchants commonly use Stripe, Adyen, or category-specialised processors. The gateway mix on BC is a strategic decision, not a default. |
| Fee implications | Gateway fees range from 1.4-3.5% of revenue. A wrong gateway choice can cost 50-150 bps of margin. Pair this card with the gateway dashboards’ fee reports to see effective processing cost; for high-AOV stores ($100+ AOV) the savings from a 50-bp better gateway are material. |
| B2B Edition note | B2B Edition supports invoice / Net-30 / ACH options that don’t flow through credit-card gateways. Those orders show under paymentMethod = "Bank Deposit" or "Manual / Phone Order" rather than a gateway. |
| Time window | 30D (rolling 30 days) |
| Alert trigger | None at this card; gateway-specific alerts live on cards like BC Decline Rate. |
| Roles | owner |
Calculation
Calculated automatically from your BigCommerce data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A US homewares brand on BigCommerce Pro using a mixed gateway stack, last 30 days from 14 Mar 26 to 12 Apr 26.| Gateway | Revenue | Share | Approx fee | Effective cost |
|---|---|---|---|---|
| Stripe | $182,400 | 53.8% | 2.9% + $0.30 | $5,289 |
| BigCommerce Payments (powered by PayPal) | $94,200 | 27.8% | 2.59% + $0.49 | $2,439 |
| PayPal Express | $42,100 | 12.4% | 3.49% + $0.49 | $1,469 |
| Square (POS) | $14,800 | 4.4% | 2.6% + $0.10 | $385 |
| Manual / Phone Order (B2B) | $5,400 | 1.6% | $0 | $0 |
| Total | $338,900 | 100% | $9,582 (2.83% blended) |
- 53.8% on Stripe is healthy concentration. Stripe is rate-competitive (2.9% + 1M/year processed.
- 27.8% on BigCommerce Payments is strategically interesting. BC Payments (powered by PayPal) is at 2.59% + 0.30. For a store with 50.** Below that, Stripe is cheaper per dollar.
- PayPal Express at 12.4% is the most expensive shelf in the mix. 3.49% on 1,469/month; if the merchant could route those orders through Stripe instead, they’d save ~$250/month. The reason to keep PayPal as a button: a meaningful fraction of customers will not enter a credit card, they’ll only buy if they can use their PayPal balance. Removing PayPal typically loses 5-10% of orders. Trade-off worth measuring per store.
- Square POS at 4.4% is fine. Square is the standard POS choice; rate is competitive. If POS were a bigger share (>15%), worth comparing against BC POS Payments.
- B2B Manual / Phone Order at 1.6% carries no gateway fee. Healthy structural cost-saving for B2B stores; the operational cost is in invoice management, not in payment processing.
- Audit blended effective rate. Multiply per-gateway revenue by per-gateway fee, divide by total. Most BC stores blend 2.6-3.1%; above 3.1% suggests a gateway mix-shift opportunity.
- Compare Stripe vs BC Payments vs Adyen quotes. For stores processing >$2M/year, all three offer custom volume pricing; the savings can be 30-80 bps.
- Test removing PayPal as a button in a 4-week A/B (50% of traffic see PayPal, 50% don’t). Most stores find PayPal contributes 5-10% of orders that wouldn’t otherwise convert; the math is whether incremental orders × margin > PayPal fee differential.
- Audit decline rate per gateway. A gateway with 0.8% decline rate vs another’s 2.1% can be the difference between two campaigns that look identical on this card. Pair with BC Decline Rate split by
paymentMethod. - For B2B-heavy stores, audit ACH vs card mix. ACH (BC supports via Plaid integration) is typically 0.8-1.2% vs 2.6-3.5% on card; pushing B2B to ACH saves real money on high-AOV invoices.
Sibling cards merchants should reference together
| Card | Why pair it with Revenue by Payment Gateway |
|---|---|
| Payment Methods | Order count by method (this card is revenue). Together they show whether high-AOV orders concentrate on a particular gateway. |
| Total Revenue | The denominator that anchors the gateway shares. |
| BC Decline Rate | Per-gateway decline rates, the right counterpart to gateway revenue for ROI analysis. |
| Financial Status Breakdown | The state-level view. Gateway-specific decline patterns show in declined share. |
| BC Channel Revenue Mix | Channel-by-gateway. POS uses different gateways than web; channel mix changes the gateway mix. |
| Refund Value | Refunds also flow through gateways; net revenue per gateway differs from gross. |
stripe.stripe_total_revenue | Stripe-side reconciliation. Should match this card’s Stripe row to within ~1%. |
paypal.pp_total_volume | PayPal-side reconciliation for the BC Payments + PayPal Express slices. |
Reconciling against the vendor’s own dashboard
Where to look in BigCommerce Control Panel: Settings → Payments shows the active gateways and their configuration but not revenue by gateway. Analytics → Sales on Plus / Pro / Enterprise has a “Revenue by payment method” tile that closely mirrors this card. For per-gateway financial reconciliation, use the gateway’s own dashboard:- Stripe Dashboard → Reports → Sales summary
- PayPal Business → Activity → Reports
- BigCommerce Payments → embedded BC report
- Square Dashboard → Reports
- Adyen → Customer Area → Reports
| Reason | Direction |
|---|---|
| Settlement timing. Gateway-side reports show captured + settled charges; we show order-time totals. A captured-but-not-yet-settled order shows here today, on the gateway side tomorrow. | Vortex IQ slightly LEADS gateway reports |
| Refunds. We show gross order-time revenue; gateway reports often show net (gross - refunds). | Vortex IQ HIGHER than net-of-refunds gateway report |
| Currency / FX. Gateway-side may report in a single settlement currency; we report at order-time native currency. | Mixed |
| Failed captures. Orders that authorised then failed to capture may show here as “captured” briefly before status updates; gateway reports never show them. | Boundary effects |
Subscription / recurring. BC’s subscription apps may use a different processor that doesn’t show under the standard paymentMethod field. | Mixed |
| Time zone. UTC vs gateway TZ. | Boundary effects |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
stripe.stripe_total_revenue | Stripe-side total should match this card’s Stripe row | Settlement timing, refund treatment, FX. |
paypal.pp_total_volume | PayPal-side volume should reconcile to BC Payments + PayPal Express rows | PayPal-side may aggregate differently if BC Payments uses PayPal as the back-end processor. |
shopify.gateway_revenue(planned)adobe_commerce.gateway_revenue(planned)