WooCommerce payments that aren’t locked to one bank.
MevvPos connects your WooCommerce store to a multibank payment layer instead of a single bank. Define more than one virtual POS, and each card is routed by its BIN to the bank that issued it — so your customer sees that bank’s own instalment plan. Thirteen banks and payment providers are supported today, and the BIN database behind the routing is kept current from our own servers. For stores selling outside Türkiye, eight international providers can be connected as well.
How it works
The engine runs with or without WooCommerce. What follows is the configuration a shop actually fills in.
Pick the bank or provider and the screen changes with it: a Turkish bank brings a gateway address, a BIN list and instalment options; an international provider works over its own API and has neither. Test mode is a switch, not a second set of keys to keep straight.
A commission rate per instalment count, up to twelve. Leave one empty and that option is simply not offered to the customer. The free edition shows at most three instalments and the screen says so out loud instead of hiding the rates you typed.
All prices include VAT.
1 USD = 49,9178 ₺ (İşbank rate)
Coverage
Thirteen banks and payment providers take payments today — each with its own gateway address, its own BIN ranges and its own instalment terms.
Beyond Türkiye
For stores selling outside Türkiye, MevvPos can also connect to eight providers over their own hosted pages, so card details never touch your site. These are not tied to a bank: they carry no BIN routing and report no instalment plans, which stay a Turkish-market feature. None of the eight has yet been verified end to end with a live merchant account — the flows, field names and signature algorithms follow each provider’s own published documentation, so read them as ready to connect and test against your sandbox rather than as proven in production.
Why routing matters
Banks give their own cardholders better instalment terms. With a single virtual POS you can only ever offer one bank’s terms to everyone — and the rest of your customers see a worse plan than their bank actually offers them.
One POS· one set of terms
A stale BIN list is worse than none: it sends a card to the wrong bank confidently, and the shopper sees terms that bank never offered.
Many POS· one plugin
And the question no one else answers: what does twelve instalments actually cost you? The report shows the commission burden next to the revenue.
What it does
Each capability exists to remove a specific operational friction.
İşbank, Akbank, Halkbank, QNB, Şekerbank, TEB, Ziraat, Garanti BBVA, VakıfBank, plus iyzico, PayTR, Craftgate and Sipay — one plugin, one settings screen.
Each card is recognised from its first six digits and sent to the bank that issued it, so the customer gets that bank’s own instalment plan instead of a generic one.
Three sources merged and kept current from our servers. A stale list sends cards to the wrong bank; ours updates weekly.
Set the instalment counts and surcharge rates separately for every POS you define.
Daily revenue, success rate and instalment split — with a per-bank and per-POS breakdown, plus the commission burden of each instalment tier.
Card number, expiry and CVV are never written to your database.
Whichever checkout page your store uses, the card option is there. On the WooCommerce Checkout block the instalment table and its surcharge are handled just as they are on the classic page.
Selling outside Türkiye, MevvPos can also connect to Stripe, PayPal, Mollie, Square, Authorize.Net, Checkout.com, Razorpay and Paystack — each over its own hosted page, so card details never touch your site.
A POS can hold the amount on the card instead of charging it, and you capture it — in full or in part — from the order screen when the parcel goes out, or release it if it cannot. The option appears only where the provider genuinely supports it: the NestPay bank family, Stripe, Authorize.Net and Checkout.com. The other banks are not offered a setting that would fail at the gateway.
Create a link for an amount from the admin and send it to the customer. They pay on the ordinary checkout, so the same BIN routing, instalment table and 3-D Secure apply — it is not a second, weaker payment path. The link carries a random token, expires, and stops working the moment it is paid.
Five rules, each switched on separately: attempts per address, attempts per card, consecutive failures, a Turkish-issued card billed abroad, and an amount ceiling. Each can flag the order, hold it for review or decline it. Neither the address nor the card number is stored — only a digest salted with your own site key, because a fraud screen that keeps card data is a second card database.
Product information