Skip to main content
Card class: Non-HeroCategory: Ecommerce Platform

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 countsSUM(totalIncTax) per paymentMethod value over the last 30 days, with each order attributed to whichever gateway processed its payment.
VAT / tax treatmentTax-inclusive (uses totalIncTax).
ShippingIncluded (part of totalIncTax).
DiscountsAlready deducted (post-discount customer-billed total).
RefundsNot deducted (gross gateway-attributed revenue). To get refund-net per gateway, subtract gateway-side refund volume from the gateway dashboard.
Cancelled / voided ordersIncluded if the order’s payment status reached captured; excluded if it was declined or voided. The boundary depends on BC’s status transition timing.
CurrencyMulti-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 / sourcesAll 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 ShopifyShopify 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 implicationsGateway 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 noteB2B 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 window30D (rolling 30 days)
Alert triggerNone at this card; gateway-specific alerts live on cards like BC Decline Rate.
Rolesowner

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.
GatewayRevenueShareApprox feeEffective cost
Stripe$182,40053.8%2.9% + $0.30$5,289
BigCommerce Payments (powered by PayPal)$94,20027.8%2.59% + $0.49$2,439
PayPal Express$42,10012.4%3.49% + $0.49$1,469
Square (POS)$14,8004.4%2.6% + $0.10$385
Manual / Phone Order (B2B)$5,4001.6%$0$0
Total$338,900100%$9,582 (2.83% blended)
What’s interesting:
  1. 53.8% on Stripe is healthy concentration. Stripe is rate-competitive (2.9% + 0.30),featurerich(Radarfraud,3DSadaptive,Apple/GooglePaynative),andhandles 950.30), feature-rich (Radar fraud, 3DS adaptive, Apple/Google Pay native), and handles ~95% of card brand acceptance. Stores typically pay slightly less by negotiating volume rates above 1M/year processed.
  2. 27.8% on BigCommerce Payments is strategically interesting. BC Payments (powered by PayPal) is at 2.59% + 0.49,thepertransactionfeeishigherthanStripes0.49, the per-transaction fee is higher than Stripe's 0.30. For a store with 90AOVtheeffectiverateis3.1390 AOV the effective rate is 3.13% on BC Payments vs 3.23% on Stripe. **BC Payments wins on margin for AOV above ~50.** Below that, Stripe is cheaper per dollar.
  3. PayPal Express at 12.4% is the most expensive shelf in the mix. 3.49% on 42k=42k = 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.
  4. 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.
  5. 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.
The strategic playbook for gateway mix:
  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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

CardWhy pair it with Revenue by Payment Gateway
Payment MethodsOrder count by method (this card is revenue). Together they show whether high-AOV orders concentrate on a particular gateway.
Total RevenueThe denominator that anchors the gateway shares.
BC Decline RatePer-gateway decline rates, the right counterpart to gateway revenue for ROI analysis.
Financial Status BreakdownThe state-level view. Gateway-specific decline patterns show in declined share.
BC Channel Revenue MixChannel-by-gateway. POS uses different gateways than web; channel mix changes the gateway mix.
Refund ValueRefunds also flow through gateways; net revenue per gateway differs from gross.
stripe.stripe_total_revenueStripe-side reconciliation. Should match this card’s Stripe row to within ~1%.
paypal.pp_total_volumePayPal-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
Why our number may legitimately differ from each gateway’s report:
ReasonDirection
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
Cross-connector reconciliation:
CardExpected relationshipWhat causes legitimate divergence
stripe.stripe_total_revenueStripe-side total should match this card’s Stripe rowSettlement timing, refund treatment, FX.
paypal.pp_total_volumePayPal-side volume should reconcile to BC Payments + PayPal Express rowsPayPal-side may aggregate differently if BC Payments uses PayPal as the back-end processor.
Same-metric documentation cross-reference:

Known limitations / merchant FAQs

Should I switch from Stripe to BigCommerce Payments? Run the math, don’t switch on assumption. BC Payments is 2.59% + 0.49;Stripeis2.90.49; Stripe is 2.9% + 0.30. The crossover AOV is around 50,above50, above 50 AOV BC Payments wins; below it Stripe wins. Most stores process at multiple AOV bands; the right answer is whichever weighted average is lower. Also factor in feature parity, Stripe Radar fraud is generally better than BC Payments’ equivalent. Why is PayPal so expensive at 3.49%? PayPal Express’s fee is structurally higher than card-rails because it includes the PayPal-balance routing premium and PayPal’s risk-bearing. The acceptance value is real (5-10% of customers will only buy with PayPal balance). Don’t optimise PayPal away on margin alone; measure incremental order contribution first. Can I run Stripe AND BigCommerce Payments at the same time? Yes. BC supports multiple gateways simultaneously; the storefront can route based on customer region, currency, payment method, or A/B test logic. Common pattern: Stripe for cards, BigCommerce Payments / PayPal for digital wallets, Square for POS, ACH for B2B. My gateway revenue report shows 5% less than my Stripe dashboard, why? Several normal reasons. (1) Refund treatment: this card is gross; Stripe may show net. (2) Settlement timing: this card uses order-time; Stripe may use settlement date. (3) Currency: multi-currency stores see FX-conversion differences. (4) Subscription / recurring: recurring charges may flow through a different gateway integration than retail. Reconcile day-by-day to identify the cause. Should I worry about a 10% concentration on a single gateway? Concentration is a feature, not a bug, up to a point. 50-70% on a primary gateway is normal and economically efficient. Above 80% concentration creates outage risk: if Stripe has a 4-hour outage, you lose 80% of revenue for the duration. Most stores keep a 15-30% secondary as a fallback for exactly this reason. Does BC support Klarna / Afterpay / Affirm? Yes via integration apps. BNPL providers typically charge 4-6% (higher than cards) but can lift conversion by 10-25% on AOV-above-$100 categories. The fee differential is justified if the incremental orders × margin > the BNPL fee differential. The right BNPL test is a 4-week A/B with vs without; many stores find BNPL is not net-positive on smaller AOV. My B2B gateway shows up as “Manual / Phone Order”, what’s that? B2B Edition’s invoice flow. Customer orders, you generate an invoice, customer pays via ACH / wire / cheque, you mark the order paid manually. Zero gateway fee, slow cash conversion. Many B2B stores prefer this because invoice billing matches B2B accounting workflows. Can I see fee data on this card? Not directly; this card is gateway revenue, not gateway cost. For fee data combine this card with each gateway’s own fee report. We are working on a “blended cost of payment processing” derived card; track the V2 backlog. Why does my marketplace channel show one aggregated gateway value? Because marketplaces (Amazon Pay, eBay Managed Payments) handle their own processing and report a single payout to BC. The order-level gateway is “Marketplace Pay” or similar, with no further breakdown. To analyse marketplace cost, look at the marketplace seller dashboard. Should I migrate from Cybersource to a newer gateway? Often yes, but with care. Cybersource is enterprise-grade but its fee schedule has structural costs (gateway + processor + acquirer separately) that can stack to 3.5-4.5% blended. Modern flat-fee gateways (Stripe, Adyen) are usually cheaper for sub-Enterprise volume. Cybersource is still strong for global multi-currency and high-volume Enterprise; for typical mid-market BC stores, simpler gateways win on cost.

Tracked live in Vortex IQ Nerve Centre

Revenue by Payment Gateway is one of hundreds of KPI pulses Vortex IQ tracks across BigCommerce and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.