QuickPay.ge for WooCommerce: First Look at Georgia's Multi-Bank Checkout Plugin

If you run a WooCommerce store based in Georgia (the country, not the U.S. state) and you're tired of juggling separate integrations for Bank of Georgia, TBC, and PayPal, a new plugin just landed on the WordPress.org repository that tries to solve exactly that problem: QuickPay.ge for WooCommerce.

This is a first-coverage look based on the plugin's WordPress.org listing and the setup flow it describes. We'll flag clearly where information — like pricing — simply isn't public yet.

What QuickPay.ge Actually Does

QuickPay.ge is not itself a bank or a card acquirer. It's a checkout aggregator layer that sits between your WooCommerce store and the payment processors you already have merchant accounts with. Instead of installing and configuring separate WooCommerce extensions for Bank of Georgia's iPay, TBC's e-commerce gateway, PayPal, and any crypto processor you use, you install one plugin and connect QuickPay.ge to those existing accounts through a dashboard at quickpay.ge.

At checkout, customers see a single QuickPay.ge-hosted payment page rather than being bounced between different bank redirect pages with inconsistent branding. Because the page is hosted by QuickPay.ge rather than your own server, card data never touches your WooCommerce install directly — which simplifies PCI DSS scope for the merchant, similar to how Stripe Checkout or PayPal's hosted pages work.

The processors it currently bundles

• Bank of Georgia (merchant/iPay accounts)
• TBC Bank e-commerce merchant accounts
• PayPal
• Crypto payment providers (the listing doesn't name a specific processor, so treat this as "crypto support exists" rather than a guaranteed named coin list until you test it)

This is the plugin's real differentiator: nothing else in the WooCommerce ecosystem natively speaks to both Bank of Georgia and TBC in one settings screen.

How Setup Works

Based on the listed installation flow:

1. Install and activate the plugin from the WordPress.org repository (search "QuickPay.ge" or upload the zip from the plugin page).
2. Create an account at quickpay.ge separately from your WordPress admin.
3. Connect your existing Bank of Georgia, TBC, PayPal, and/or crypto merchant credentials inside the QuickPay.ge dashboard — you still need those underlying merchant accounts; QuickPay.ge doesn't replace the need to be approved by Bank of Georgia or TBC first.
4. Generate API keys from the QuickPay.ge dashboard and paste them into the WooCommerce payment settings under the QuickPay.ge gateway tab.
5. Choose which of your connected processors appear at checkout, and in what order.
6. Test with a live transaction (there's no indication of a sandbox/test mode in the listing, so budget time for a real small-value transaction before launch).

The practical implication: this plugin saves you integration and maintenance work, not underwriting work. You still need to be a registered business that qualifies for a Bank of Georgia or TBC merchant account, which is its own multi-week process if you don't already have one.

Pricing: Not Published Yet

This is the biggest open question. Neither the WordPress.org plugin page nor the standard listing metadata publishes a fee schedule, and quickpay.ge itself doesn't post transaction fees or a monthly tier chart in any research we could surface. The plugin itself is free to install (as is standard for WordPress.org-hosted plugins), but:

• It's unclear whether QuickPay.ge charges a per-transaction markup on top of what Bank of Georgia/TBC/PayPal already charge you.
• It's unclear whether there's a monthly SaaS fee for using the aggregation dashboard.
• It's unclear whether pricing differs for crypto vs. card rails.

If you're evaluating this today, treat pricing as a direct question to ask QuickPay.ge support before connecting a live merchant account, not something to assume is free just because the WordPress plugin download is free. Aggregator layers like this typically take a small percentage or fixed fee per transaction on top of the underlying processor's cut — confirm this in writing before your first sale.

Concrete Use Cases

• A Tbilisi-based apparel store currently only accepting Bank of Georgia cards and losing sales from customers who bank with TBC — adding QuickPay.ge lets them accept both without maintaining two separate WooCommerce gateway plugins.
• A Georgian SaaS or digital goods seller wanting to accept PayPal from diaspora customers abroad alongside local bank cards, without building a custom checkout branching logic.
• A store experimenting with crypto payments that doesn't want to install and maintain a separate crypto gateway plugin alongside their bank integrations.
• An agency managing several Georgian WooCommerce clients who wants one consistent checkout UI to support across sites instead of learning the quirks of each bank's individual WooCommerce extension.

What it's not a fit for: stores outside Georgia, or stores whose customers pay almost exclusively via cards issued by banks outside the Bank of Georgia/TBC ecosystem. The value proposition is entirely about the local Georgian banking layer.

How It Compares

	QuickPay.ge for WooCommerce	Stripe for WooCommerce	Square for WooCommerce	2Checkout (Verifone)
Published pricing	Not published — must contact quickpay.ge	2.9% + $0.30 per transaction (standard U.S. rate; varies by country)	2.6% + $0.10 per transaction (in-person), 2.9% + $0.30 online	~3.5–6% depending on plan and region, plus monthly fees on some tiers
Local Georgian bank support	Yes — native Bank of Georgia and TBC integration	No — relies on Stripe's own acquiring, not available for GEL settlement in Georgia in most cases	No — not available as a merchant of record in Georgia	Indirect — works globally but no direct Bank of Georgia/TBC merchant account linkage
Crypto support	Yes, via connected crypto processors	No native support	No native support	No native support
PCI scope	Reduced — hosted payment page	Reduced — Stripe Elements/Checkout hosted fields	Reduced — hosted checkout	Reduced — hosted checkout
Best for	Georgia-based merchants needing multiple local banks in one checkout	International merchants wanting a globally trusted, well-documented gateway	Merchants who also use Square in physical retail locations	Merchants needing broad international card acceptance with less local bank nuance

Should You Install It Today?

If you already hold merchant accounts with Bank of Georgia and/or TBC and you've been maintaining two separate WooCommerce gateway plugins to support both, QuickPay.ge is worth testing this week — the consolidation alone is a real time-saver, and the plugin is free to try since you're not paying anything to WordPress.org for it.

The honest caveat: this is a new listing with limited public track record, no visible pricing, and no confirmed sandbox/test mode. Before routing real customer payments through it, get pricing confirmed in writing from QuickPay.ge support, run a real low-value test transaction, and check the WordPress.org support forum for the plugin to see how responsive the developer is to bug reports — that responsiveness is usually the best early signal of whether a young payment plugin is safe to depend on long-term.

If your store operates outside Georgia or your customers don't bank with Bank of Georgia or TBC, there's no reason to look at this over Stripe or Square — the entire value proposition is local-bank aggregation, and that advantage disappears outside that market.