Choosing a Payment Gateway: Virtual POS, Stripe and Local Providers
Virtual POS, local payment providers, and Stripe compared: what multi-currency actually requires, and which setup fits which business, without price guesses.
rabbitclip teamPublished: 5 min read
Short answer
If you sell only within one country in one currency, a bank's virtual POS or a local payment provider such as iyzico or PayTR is enough; if you also sell abroad, or need multiple currencies, you need an international setup such as Stripe, or a local provider with genuine multi-currency support.
Choosing a payment gateway is not a decision about which bank works in the background; it is a decision about what the customer sees on the checkout screen, which cards they can pay with, and how quickly the money reaches the account.
The difference between a virtual POS and a payment provider
A virtual POS is a payment acceptance method issued directly by a bank and tied to that bank's own infrastructure; it usually comes with lower transaction cost but setup and integration are a more technical process.
Payment providers such as iyzico or PayTR combine several banks' POS terminals behind a single integration; setup is faster, and managing instalment options and different card types from one dashboard is easier.
When multi-currency actually matters
For a shop working in a single currency, this simply does not come up. For a shop selling abroad, or planning to, letting the customer pay in their own currency (GBP, EUR, USD) directly affects conversion.
Providers like Stripe support multi-currency natively; support varies between local providers, so it needs verifying against that provider's current feature list before you choose.
What criteria the decision should turn on
There is no single 'best' option; the decision follows the actual needs of the business.
- Domestic only, or selling abroad too
- Does instalment payment matter to your customers
- Is the settlement time (usually a few days) fine for your cash flow
- How ready is the technical integration with your current e-commerce setup
A flooring manufacturer's setup
A flooring manufacturer served both domestic dealer orders and a limited number of overseas customers from one site; a local provider handled domestic orders, and a separate multi-currency method was set up for the overseas order flow.
Running both methods on one site is entirely workable; what matters is that each customer pays in their own currency, in a way they already trust.
How hard is it to switch
Switching payment providers is a limited-scope integration job that does not touch the rest of the site; but going live without testing first is a genuine risk. The switch should be planned so the order flow does not break mid-transition.
Decision criteria: which question points to which provider
Choosing a payment provider depends far more on how you sell than on a comparison of commission rates. If you sell only in one country, in one currency and with instalments, the domestic providers and the bank's own gateway come to the fore; instalment options and local card habits are decisive there. If you sell abroad and in several currencies, an international provider's multi-currency and local payment method support carries more weight.
The second criterion is where the payment flow takes place. A flow that keeps the customer on your own page protects conversion but brings the security obligations to you; a flow that redirects to the provider's page makes setup easier. The third criterion is refunds and dispute handling: how quickly refunds move in the dashboard and how disputes are managed directly affects the team's time as monthly volume grows.
When a spa chain lined up these criteria it found the answer quickly: because instalments were decisive for package sales it went with a domestic provider, and separately enabled multi-currency support on the card payment page for its foreign guests.
- Sales geography and currency
- Instalments and local card habits
- Payment flow on your site or on the provider's
- Speed of refunds and dispute handling
- Accounting and invoicing integration
Common mistakes and a migration plan
The most common mistake is looking only at the commission rate and missing the hidden costs: refund fees, currency conversion spreads, settlement time and fixed monthly charges can change the picture once added up. The second is going live without any testing in the sandbox; failed payments, 3D Secure errors and refund scenarios learned in production cost customers.
The third mistake is forgetting saved cards and subscriptions when switching providers. If there are recurring payments, the move should be made by telling customers in advance and running the two providers side by side for a while.
The migration plan can stay simple: open the new provider on a low-volume product group first, watch the error rate and settlement time for a month, then move the remaining products. The old provider is not switched off during that period.
Choosing a payment gateway may look like a technical detail, but it directly affects the trust a customer feels at the moment of paying; the right combination depends on your domestic/international mix and your cash flow needs, and that is worth working out together.
FAQ
What is the key difference between local providers like iyzico and PayTR?
They serve a similar function; instalment options, integration tools and transaction terms differ, so current features should be checked with the provider directly.
Do you need a bank to get a virtual POS?
Yes, a virtual POS is issued directly by a bank; payment providers meet the same need without requiring a separate bank agreement.
Is Stripe usable in Turkey?
It depends on usage terms and company structure; current availability should be checked in Stripe's own documentation before starting.
Does switching payment gateways later break the site?
Not if planned properly; it is a limited-scope integration change that should be verified in a test environment before going live.
