When merchants talk about payment fees in WooCommerce, they are usually referring to the costs applied each time a customer completes a transaction at checkout. These fees are not created by WooCommerce itself. They are the result of how online payments are processed through card networks, banks, and payment gateways.
WooCommerce acts as the commerce platform, while payment gateways handle the actual movement of money. The fees you see are the combined outcome of several parties involved in approving, routing, and settling a payment.
Understanding these layers is essential if you want to make sense of why different payment methods, gateways, or transaction types result in different costs.
WooCommerce acts as the commerce platform, while payment gateways handle the actual movement of money. The fees you see are the combined outcome of several parties involved in approving, routing, and settling a payment.
Understanding these layers is essential if you want to make sense of why different payment methods, gateways, or transaction types result in different costs.
The main components of WooCommerce payment fees
Most WooCommerce payment fees are built from three core components:
- Card network and interchange fees
- Gateway processing fees
- Additional charges linked to how a payment is authorised and captured
Not every payment includes all three in the same way. The structure depends on the payment method used and how the transaction flows through checkout.
Card network and interchange fees
For card payments, a significant portion of the total fee comes from interchange and card network costs.
Interchange fees are set by the card networks and paid to the customer’s bank. They compensate the bank for issuing the card, managing risk, and guaranteeing the payment. These fees vary based on factors such as:
- Card type (debit or credit)
- Consumer or business card
- Domestic or international card
- Online versus in-person usage
In addition to interchange, card networks charge their own assessment or scheme fees. These cover the operation of the card network itself, including authorisation, routing, and security infrastructure.
These fees exist regardless of which payment gateway you use. They are embedded into almost every card transaction processed through WooCommerce.
Gateway processing fees
Payment gateways add their own processing fees on top of card network and interchange costs. This is the portion of the fee that merchants most commonly see advertised by providers.
Gateway processing fees typically cover:
- Payment authorisation and capture
- Fraud detection and risk checks
- Tokenisation and secure storage of payment details
- Technical infrastructure and compliance
While gateways often present these fees as a single percentage plus a fixed amount, they are layered on top of underlying card costs rather than replacing them.
Authorisation vs capture-related charges
Not all payment fees are triggered in the same way. In some WooCommerce setups, authorisation and capture happen at different moments.
Authorisation confirms that the customer has sufficient funds and that the card or account is valid. Capture is the step where the money is actually transferred.
In most standard WooCommerce checkouts, these steps happen immediately and feel like a single action. However, certain flows can introduce differences in how fees are applied, such as:
- Delayed capture after order review
- Partial captures for split shipments
- Failed or expired authorisations
These scenarios can affect how fees are calculated or whether certain charges are applied, depending on the gateway and payment method.
Why different payment methods have different fees
Not all payment methods rely on the same infrastructure. This is why WooCommerce payment fees can vary significantly between cards, wallets, and bank-based payments.
Card payments rely on card networks, issuing banks, and acquiring banks. Each layer introduces its own cost.
Wallets often sit on top of card infrastructure, which means their fees usually include card-related costs plus additional processing layers.
Bank-based payment methods follow a different path entirely, using direct account-to-account transfers rather than card networks. As a result, their fee structures are formed differently.
These structural differences explain why fees vary, without implying that one method is inherently better or worse than another.
What payment fees do not explain
Payment fees are often blamed for issues they do not cause. In particular, fees are not responsible for payments being declined, blocked, or failing at checkout.
Declines and failures usually happen earlier in the payment flow, during authorisation, risk assessment, or customer-side validation. They can be triggered by insufficient funds, bank rules, fraud checks, incorrect details, or technical interruptions.
The cost structure of a payment does not influence whether a transaction is approved or rejected. Understanding this distinction is important, because it helps merchants avoid misdiagnosing checkout problems and looking for solutions in the wrong place.
How this fits into the wider WooCommerce payments ecosystem
Payment fees are just one part of a broader payments setup that includes gateways, payment methods, checkout flows, and operational decisions.
If you are looking for a high-level view of how all these elements interact, the Fees and Transaction Costs authority guide provides the strategic context. This article is intended to explain the mechanical side of how fees are formed, rather than how to optimise or compare them.
For readers focused on choosing between providers or comparing costs directly, a dedicated gateway comparison guide addresses that decision-making layer separately.
If you want to understand how alternative payment methods fit into WooCommerce with a different fee structure, the pay-by-bank explainer provides a deeper look at bank-based payments within the WooCommerce ecosystem.
