Can I have different fee based on which payment gateway customer selects on the checkout?

FAQ & Troubleshooting · 2 min read · Updated May 21, 2026

you want different fees applied at checkout based on which payment gateway the buyer picks — for example, a small surcharge if they pay by PayPal but no surcharge if they pay by Stripe — and you want to know whether Tickera supports this.

Short answer

Not directly in Tickera, but yes when running with Bridge for WooCommerce plus a small WooCommerce extension that adds payment-gateway-based fees.

The recipe

  1. Install Tickera + WooCommerce + the Bridge for WooCommerce add-on so your tickets become WooCommerce products.
  2. Install the official WooCommerce extension Payment Gateway-Based Fees.
  3. Configure the per-gateway fee in WooCommerce → Settings → Payments — each enabled gateway gets a fee setting.
  4. Done. The fee shows up on the checkout the moment the buyer picks the gateway, and is added to the order total.

Why you can’t do this in Tickera standalone

Tickera’s standalone checkout has a single fee per ticket type (or a flat order-level fee), not per-gateway logic. The WooCommerce ecosystem has a richer fee/coupon model that handles per-gateway rules natively — leveraging that via Bridge is cleaner than building custom code.

Use cases this solves

  • Passing on PayPal’s fee. PayPal charges ~3% per transaction; if you add a small per-PayPal-checkout surcharge, you can recover that cost without inflating Stripe transactions.
  • Discount for offline / bank transfer. Reverse direction — offer a small discount when buyers pay by offline bank transfer (no card processor fee for you).
  • Currency-conversion fees. Different gateways handle currency conversion differently; per-gateway fees let you stabilize what you net.

Alternatives if you don’t want WooCommerce

If you’d rather not run WooCommerce, you can implement custom per-gateway fees via Tickera’s hooks and filters — specifically by hooking into the order-total calculation and adding logic based on the selected payment method. This is developer-level work.

Related

Was this article helpful?

Yes — great. No or partially? Tell us what was missing — we read every message and use it to improve these docs.