eCommerce
Payment gateway vs payment processor vs acquirer: the 3-layer stack explained
A payment gateway encrypts and transmits your customer's card data. A payment processor routes that data between your bank and the card network and settles the funds. An acquirer (your merchant bank) holds the settlement account and carries the fraud liability. Most platforms bundle all three, but knowing which layer a fee or dispute lives on tells you who to call and what to fix.
A payment gateway is the front-end software layer that captures, encrypts, and tokenizes the card at checkout. A payment processor is the back-end router that builds the authorization message, talks to Visa, Mastercard, and Amex, and returns approve or decline. An acquirer is the regulated bank that holds your merchant account and settles funds into your operating bank. Stripe, Adyen, Braintree, and Shopify Payments do all three jobs behind one API, which is why most DTC operators have never had to think about the distinction. Legacy stacks (Authorize.net plus Fiserv plus a separate bank acquirer) split the same three jobs across three vendors with three statements.
For an ecom operator, the gateway-vs-processor distinction matters in exactly four moments: when you renegotiate card fees, when you debug a settlement-timing issue, when you fight a chargeback, and when you cross roughly $10M in annual GMV and start running interchange-plus-plus math against your blended Stripe rate. A $30M-GMV DTC brand on Stripe at 2.9% plus $0.30 with an $85 AOV pays roughly $976,000 a year in card fees ($870K on the 2.9% plus $106K on the $0.30 stub across about 353,000 orders), before chargebacks. The same brand on a separated stack at interchange-plus-plus (interchange of ~1.8% is $540K, plus 0.25% processor margin is $75K, plus $0.15 per transaction is ~$53K) lands closer to $668K. That is roughly $308,000 a year in savings, which clears the cost of a part-time payments analyst with room to spare. Card mix shifts this 15 to 25 bps in either direction depending on premium-rewards Amex vs debit exposure. Below $5M GMV the gap is too small to bother with; the break-even sits between $10M and $20M for most DTC product mixes. When your fractional CFO or interim CFO reviews this line, the question is always "which layer of the stack is negotiable?", and the answer depends on whether you are sitting on a full-stack PSP or a separated stack.
How it works
The card-payments value chain has three distinct entities. The gateway is the software that lives between your checkout page and the card network. It captures the PAN (Primary Account Number), encrypts it, tokenizes it so your own systems never store raw card data, runs the 3D Secure challenge if the issuer requires one, and forwards the authorization request downstream. Examples sold standalone: Authorize.net, NMI, Spreedly. Inside a full-stack provider, this is Stripe Elements, Stripe Checkout, Adyen Drop-in, or the Shop Pay checkout.
The processor receives the authorization request from the gateway, builds the ISO 8583 message (or the modern scheme API equivalent), and routes it to the card network. The network forwards it to the issuing bank. The issuer approves or declines, the answer comes back through the same path, and the processor returns it to the gateway. The processor also handles clearing and settlement messaging at end-of-day. Examples sold standalone: Fiserv (First Data), TSYS, Worldpay, Chase Paymentech. Inside Stripe, this is the PaymentIntents API.
The acquirer is the regulated bank that holds your merchant account. It receives funds from the card networks after clearing, deducts interchange and scheme fees, and settles the net amount into your operating bank account on the agreed payout schedule. The acquirer bears the credit and regulatory risk on your merchant activity. Examples: Wells Fargo Merchant Services, Bank of America Merchant Services, Worldpay's acquiring arm. In most markets Stripe, Adyen, and Shopify Payments hold their own acquiring licences (or operate as a payfac with a sponsoring acquirer in the background), so you never see this layer. The collapse of those three layers into a single counterparty is the entire commercial pitch of a full-stack PSP: one API, one dashboard, one fee, one place to fight a chargeback, in exchange for a blended rate well above the underlying interchange cost.
Common triggers
- Renegotiating card fees above $5M monthly volume. Stripe will quote interchange-plus if you ask; the conversation needs you to point at the processor margin and the acquirer margin as the two negotiable lines on a separated stack, or the blended rate on a full-stack PSP.
- Crossing $10M to $20M in annual GMV. This is the break-even where interchange-plus-plus on a separated stack starts to beat flat-rate full-stack by 20 to 60 basis points, depending on card mix.
- Debugging settlement timing. The processor and acquirer control payout cadence, not the gateway. Stripe US is T+2 by default; Shopify Payments US is daily; Adyen offers daily or weekly; a separated stack matches the acquirer contract (usually T+1 or T+2).
- Fighting a chargeback on a legacy stack. Chargebacks live with the acquirer or processor, never the gateway. On a separated stack, dispute fees show up on the acquirer's statement and the response portal is a different login from your gateway. On Stripe or Shopify Payments, the dispute UI is unified inside one dashboard.
- Running multi-processor smart routing above $50M GMV. Enterprise DTC brands run Stripe plus Adyen plus Braintree through a smart router (Spreedly, Gravy, Primer) so a regional outage at one processor fails over to another. That only works because the gateway can sit above multiple processors.
- Switching off a non-Shopify-Payments gateway on Shopify. Shopify adds a 0.5 to 2 percent surcharge on top of your third-party gateway charges. If you are on Shopify Basic with a third-party gateway, you are paying twice; switching to Shopify Payments removes the surcharge.
The most common mistake
The biggest mistake operators make is treating "gateway" and "processor" as the same word and assuming Stripe is just one thing. The actual mistake costs money in three different shapes. First, renewing flat-rate 2.9% + $0.30 pricing past $10M GMV when an interchange-plus-plus quote from Adyen or a direct acquirer would save 20 to 60 bps. On $30M GMV that is roughly $308,000 a year before integration overhead. Second, paying the Shopify third-party gateway surcharge (0.5 to 2 percent) on top of the processor fee because the team never audited the Shopify Payments setup. Third, treating the published 2.9% headline as the full cost; the all-in effective rate after premium-card mix, cross-border, and Amex blend is usually 3.1% to 3.5% on a US DTC book. Pull your last 90 days of processor statements, divide total fees by total card volume, and compare to 2.9%. Anything over 3.0% is grounds for a rate review. If you are also carrying revenue-based financing or an MCA on top of these card fees, run the financing line through the True Interest Cost calculator before you renegotiate processing. Sometimes the cheaper basis points are on the capital line, not the card line.
Browse the full ecommerce finance glossary for every metric and money term a DTC operator needs.
Frequently Asked Questions
is a payment gateway the same as a payment processor?
No. The gateway is the front-end layer that captures and tokenizes the card at checkout. The processor is the back-end that routes the authorization request to the card networks and the issuing bank. Stripe, Adyen, and Shopify Payments do both jobs behind a single API, which is why the distinction feels invisible in those products.
does stripe have its own gateway and processor?
Yes. Stripe runs the gateway role (Stripe Elements, Checkout, Mobile SDKs that tokenize card data), the processor role (PaymentIntents that route authorization and clearing), and the payfac or acquirer role (Stripe is the merchant of record in most markets, so you are a sub-merchant under Stripe's master account). That is what full-stack means.
is shopify payments the same as stripe?
Shopify Payments is powered by Stripe under the hood in most geographies, but the merchant relationship is with Shopify. You contract with Shopify, your fees show up on your Shopify bill, and disputes are managed in the Shopify admin. Stripe is the engine, not the counterparty.
why am i being charged a transaction fee on top of my processing fee on shopify?
Because you are using a non-Shopify-Payments gateway. Shopify adds a 0.5 to 2 percent surcharge (labelled 'transaction fee' on your Shopify bill) on top of whatever your third-party gateway charges; the exact rate depends on your Shopify plan tier. If you are on Shopify Basic with a third-party gateway, you are paying twice. Switching to Shopify Payments removes the surcharge.
when should a dtc brand switch from stripe or shopify payments to a separated stack?
Usually around $10M to $20M GMV, when the basis-point math starts to matter. Run an interchange-plus-plus quote against your current blended rate using your last 12 months of card transactions broken out by card type (credit, debit, premium rewards, Amex). If the all-in number is 20 to 60 basis points lower, it is worth the operational overhead of a separated stack. Below that delta, the simplicity of full-stack wins.
