Tecof • September 22, 2026
Virtual POS Selection: iyzico, PayTR, Param Compared
In Brief
A virtual POS is the infrastructure that lets an online store collect card payments; it runs card verification, places the amount on hold and moves the money to the merchant's account. Payment institutions such as iyzico, PayTR and Param provide this through a single integration, without you having to sign a separate agreement with each bank. What most merchants look at when choosing is the commission rate alone, yet the rate is only one of three variables: the real cost does not appear until you add settlement time and the conversion loss at the payment step. As of 2026 the question is not "whose commission is lower" but "which one produces the lowest total cost for the basket structure I actually have".
Thursday morning, 10.40. A home textiles store's payment report shows this picture: over the last 30 days, 8,420 sessions reached the payment page, 2,310 people entered card details and pressed confirm, and 1,630 transactions completed successfully. In other words, 29 out of every 100 people who made it to the payment step disappeared after entering their card details. In the same month, the finance team collected quotes from three payment institutions in order to cut the commission rate by 0.2 percentage points.
The disproportion sits right there. A 0.2-point cut saves 2,400 lira on a monthly turnover of 1.2 million. Recovering a third of that 29 percent loss at the payment step changes revenue by hundreds of thousands in the same month. Choosing a virtual POS looks like a procurement negotiation, but it is really a conversion decision: whose 3D Secure flow breaks less often, who stores the card and finishes the second purchase in one tap, who tells you why a transaction failed. This article settles the decision under three headings: cost, integration and conversion.
1. What Is a Virtual POS and Who Does What in the Payment Flow?
A virtual POS is the software infrastructure that lets you take card payments without a physical device. Several parties sit in the payment flow, and knowing which question goes to whom solves half the problems you will hit in production.
What is the difference between a payment institution and a bank's own virtual POS?
A bank virtual POS works with a single bank, while a payment institution gathers the POS of many banks behind one integration. You can define the distinction like this:
- Bank virtual POS: collection through that bank's own infrastructure; it means a separate contract, a separate integration and separate reconciliation per bank.
- Payment institution (PSP): a licensed intermediary that offers several bank POS connections behind one API; one contract, one integration, one reporting screen.
- Payment facilitator / sub-merchant model: the structure used by marketplaces, where hundreds of sellers collect separately under one master account.
- POS switch: a layer that connects to several POS endpoints at once and routes each transaction to the most suitable one based on the card.
For the vast majority of small and mid-sized stores the right starting point is a payment institution: one integration covers every bank's cards and instalment campaigns. As monthly volume rises, connecting bank POS endpoints directly starts to create a commission advantage, but it brings operational load in return.
How does a payment transaction proceed, step by step?
A card transaction passes through four stages, and each stage can break in a different place. At authorisation, the card details reach the provider and the card's validity is checked. At the hold stage, the amount is blocked on the card; the money has not reached you yet. At settlement, the day's transactions are closed as a batch. In the final stage, the money is transferred to your account according to the value date in your contract.
The practical consequence of this distinction: when a customer says "the money left my account but I see no order", the transaction has most likely been authorised while the order record was never created. The fix is not a refund but completing the order record through the webhook.
Why is the 3D Secure flow both necessary and risky?
3D Secure is the step where the bank verifies that the person using the card really is the cardholder, and once verification happens, liability for fraud shifts from the merchant to the bank. In Turkey, 3D verification is widely expected on e-commerce transactions; whether non-secure transactions are available at all varies by sector and provider, and it leaves fraud risk entirely with the merchant. Confirm the current shape of this obligation for your own business model with your provider and your financial adviser.
Here is the risky side: the verification step takes the customer from your site to the bank's screen, makes them wait for an SMS and brings them back. Every hiccup — a phone out of coverage, a delayed SMS, a bank screen that renders badly on mobile — turns directly into a lost order. This is also where the most concrete difference between providers shows up: some keep verification in a layer and leave the customer on your site, others do a full-page redirect.
2. Cost: Why Is the Commission Rate Alone Misleading?
The cost of a virtual POS is the commission rate plus the time it takes the money to reach your account; leave the second out and the comparison comes out wrong. Do not put quotes side by side until every item below sits in the same table.
What items make up the commission?
- Single-payment commission: the percentage taken from a non-instalment transaction; the provider's core revenue.
- Instalment commission: an additional rate that grows with the number of instalments; at 9 and 12 instalments it can reach several times the single-payment rate.
- Fixed fee per transaction: a flat amount taken from each transaction; in stores with a low average basket it matters more than the percentage.
- Value date (hold period): the number of days before the money reaches your account; the direct cost to cash flow.
- Refund and chargeback fees: whether commission is returned on a refund, and the amount charged per dispute.
- Setup and monthly fixed fees: present in some packages, zero in others; at low turnover this can be the item that decides total cost.
Who finances the instalments, you or the customer?
The extra cost created by instalment sales either comes out of the merchant's margin or is passed to the customer as a term difference; there is no middle ground. You have to decide this according to your basket structure. If the average basket is low and the margin tight, offering six interest-free instalments erodes the margin quickly. If the average basket is high and instalments genuinely change the purchase decision, the instalment cost can be treated like a marketing expense.
Say your average basket is 1,800 lira and your gross margin is 32 percent. If the extra commission burden at six instalments is 4 percent, your margin falls to 28; if advertising already costs you 12 percent on the same basket, what remains narrows sharply. We covered the ways to raise the average basket other than instalments in our article on average order value.
How does the value date affect cash flow?
The value date is the number of days before collected money reaches your account, and in businesses with fast stock turnover it can matter more than commission. A long value date means buying new stock before the money from what you sold has arrived, which means either your own capital or financing cost. Packages offering short value dates usually carry slightly higher commission. The decision is a calculation: which one comes out cheaper at your turnover speed.
| Cost item | What it affects | Where it is critical | Question to ask in the quote |
|---|---|---|---|
| Single-payment rate | Gross margin | High volume, non-instalment | Are there volume tiers? |
| Instalment rate | Campaign margin | High average basket | Which rate at which instalment? |
| Fixed fee per transaction | Profit on small orders | Low average basket | Is it charged on failed attempts too? |
| Value date | Cash flow | Fast stock turnover | How are weekends and holidays counted? |
| Refund/dispute fee | Cost of returns | High return rates (apparel) | Is commission returned on a refund? |
| Reserve rate | Amount held back | Sectors seen as risky | What is the reserve rate and period? |
3. iyzico, PayTR and Param: Where Do They Actually Differ?
All three are licensed payment institutions, and all three cover the cards and instalment campaigns of every major bank; the difference is not in the rates but in the operating model and the product set. Because rates are set by volume, sector and negotiation, we do not print rates here; get current quotes directly from the provider, stating your own turnover.
What all three provide
- Multi-bank support: every major bank's cards and instalment campaigns through one integration.
- 3D Secure: the verified payment flow and the liability shift that follows verification.
- Management panel: transaction list, refund initiation, reconciliation report and settlement screen.
- Ready-made plugins: modules for common e-commerce platforms that need no development.
- Test environment: trying the flow with test card numbers before going live.
The differences that actually decide the choice
The decision usually comes down to one of four headings. First, the payment page experience: an embedded form that keeps the customer on your site, or a redirect to the provider's own page. Second, marketplace support: if you need to split money between several sellers, a sub-merchant structure is mandatory. Third, additional payment methods: bank transfer matching, digital wallets, cash-on-delivery integration, foreign card acceptance. Fourth, the support model: when payments stop in production, how many minutes until a human answers.
If you are building a marketplace or multi-seller model
If you collect money for several sellers and distribute it among them, a standard virtual POS is not enough; you need the sub-merchant (marketplace) model. In that model each seller is registered separately, collection pools in a master account and settlements are transferred to each seller individually. Setup takes noticeably longer than for a single store: seller approval processes, document collection and settlement reporting are added. Platform choice weighs heavily when building this structure; we described the parts of that decision that are hard to reverse in the article on mistakes made when choosing a platform.
| Decision heading | What to look at | Critical for | Cost of choosing wrong |
|---|---|---|---|
| Payment page type | Embedded form / redirect | Mobile-heavy sellers | Loss at the payment step |
| Card storage | One-tap repeat purchase | Stores with repeat customers | Friction on the second order |
| Sub-merchant support | Splitting money across sellers | Marketplaces, dealer networks | Model cannot be built; full migration |
| Foreign cards | Foreign card and currency acceptance | Cross-border sellers | Declined transactions |
| Reporting / API | Whether reconciliation data can be pulled | ERP users | Manual reconciliation load |
| Support response time | Live incident procedure | Campaign-season sellers | Collection down for hours |
4. Technical Integration: Which Method Suits You?
The integration method determines both development time and conversion at the payment step; there are three basic methods, and what separates them is whether the customer leaves your site.
Three integration types
- Hosted (redirect) payment: the customer goes to the provider's page, pays and comes back. Fastest setup and lowest technical responsibility; in exchange, visual consistency and some conversion are lost.
- Embedded form (iframe/popup): the payment form opens inside your site while card data still lives in the provider's domain. A practical balance between experience and compliance burden.
- Direct API: you design the payment form entirely. Best experience, highest responsibility: card data passing through your own systems enlarges your card security obligations.
For most stores the right answer is the embedded form. Choose the direct API only if your payment step genuinely needs a custom flow and you have the technical team to maintain it. We explained the general logic of API-based integrations from the ground up in our API article.
Why does reconciliation fail without webhooks?
A webhook is the provider notifying your system of the payment result, and the accuracy of the order depends on it. If you rely on the response returning through the customer's browser, then when the browser closes or the connection drops, no order is created even though the payment succeeded. Three rules at setup: verify the signature when a notification arrives, make the handling idempotent so the same notification arriving twice is processed once, and poll the provider for transaction status at intervals when no notification arrives.
What to test before going live
Trying only the happy path with test cards is not enough. List the failure scenarios too: insufficient funds, verification code never entered, cancellation on the verification screen, transaction timeout, partial refund, full refund, and a new order after a refund. For each one, check the screen the customer sees and the record created in your system separately. Do not skip the certificate and mixed-content state of the payment page either; a payment step that shows a browser warning stops sales on its own, as we described in our SSL article.
| Integration type | Setup time | Experience | Technical responsibility | Who it suits |
|---|---|---|---|---|
| Ready-made plugin | Hours | Medium | Low | Standard platform users |
| Redirect | 1-3 days | Medium | Low | Those wanting to go live fast |
| Embedded form | 3-7 days | Good | Medium | Most stores |
| Direct API | 2-4 weeks | Best | High | Custom flows, with a team |
5. Conversion: Where Is the Loss at the Payment Step?
Most of the loss at the payment step comes from friction, not price; a customer who has entered card details has already decided to buy, and what loses them is the flow. The items in this section usually earn more money than a commission negotiation.
How do you reduce 3D Secure losses?
Presenting the verification step in a layer that opens inside the site, rather than as a full-page redirect, reduces the loss of customers who never come back on mobile. Before the verification screen opens, tell the customer in one sentence what is about to happen ("You will enter the code your bank sends on this screen"). Leave a link showing what to do if the code does not arrive. When verification fails, bring the customer back to the payment step with card details still filled in, not to the basket.
Do card storage and one-tap checkout really work?
In stores with repeat customers, yes; they remove the card entry step entirely on the second order. Make sure the card is stored in the provider's token infrastructure and not in your system: you keep only a key, and the card number never sits with you. That structure takes both the compliance burden and the data-breach risk off you.
Instalments and error messages
Show instalment options automatically from the first six digits of the card number (BIN lookup); do not ask the customer which bank issued the card. In error messages, write what the customer can do rather than the provider's technical code: instead of "Transaction declined (05)", write "Your bank did not approve the transaction. You can try another card or call your bank." Log the reason for failed transactions at code level on your side; that is the only way to see which error concentrates at which bank. We gathered the conversion interventions outside the payment step in our article on conversion rate.
6. Risk, Compliance and the Contract Clauses to Read
The real risk in a virtual POS contract is not in the commission but in the clauses that can stop your cash flow. Reading these items before signing is cheaper than arguing about them afterwards.
How does a chargeback work?
A chargeback is the process that starts when a cardholder disputes a transaction with their bank, and through which the amount can be taken back from the merchant. Your defence rests on the strength of records: proof of delivery, shipment tracking, customer correspondence, the log showing the distance sales agreement was accepted. If you do not keep these per order, your chances of losing a dispute are high. When a store's dispute rate climbs, a provider may impose a reserve or suspend the contract.
Reserves and holds: why is your money being kept?
A reserve is the provider holding part of your settlement for a set period to cover possible refunds and disputes. It is applied more often to newly opened accounts, to pre-order sales and to business models with long delivery times. When collecting quotes, ask in writing for the reserve rate, its duration and the conditions that trigger it; if the contract contains open-ended language such as "where deemed necessary", get the limit specified.
Compliance items not to skip
- Card data security: card numbers should not sit on your server; use a token structure.
- KVKK (data protection): a privacy notice for personal data processed during payment, and a defined data-processor relationship with the provider.
- Distance sales agreement: accepted at the payment step, with the acceptance record retained.
- Prohibited and restricted products: providers do not accept every product category; share your category list before applying.
- Invoicing: alignment between the moment of collection and the moment of invoicing; this distinction matters in pre-paid sales.
Regulation on all of these can change and can be interpreted differently depending on your business model; confirm the current shape of your obligations with your own financial and legal advisers.
Choosing and Migrating a Virtual POS in Thirty Days
Thirty days is enough to cover everything from collecting quotes to going live; the condition is spending the first week on measurement. A quote received without knowing your own numbers cannot be compared.
Days 1-7: produce your own numbers
From the last three months of data, calculate: monthly transaction count, average basket, share of instalment transactions and their distribution, return rate, payment step success rate, and average order-to-delivery time. No quote means anything without these six figures. Measure this week, too, how many people you lose at each step of the payment page.
Days 8-14: collect quotes and put them in one table
Ask at least three providers for a written quote, stating your volume and sector. Ask for these six items separately in each quote: single-payment rate, instalment rates, fixed fee per transaction, value date, refund/dispute fee, reserve conditions. Put them all in one table and multiply by your own transaction distribution; "lowest rate" and "lowest total cost" usually turn out to be different providers.
Days 15-21: integration and testing
Run every successful and failed scenario in the chosen provider's test environment. Set up the webhook and test signature verification and idempotency. Settle this week how the reconciliation report will be read on the accounting side; learning that after going live is expensive.
Days 22-30: phased migration and measurement
Where possible, run the old and new virtual POS side by side for a while, or send part of your traffic to the new provider. In the first week, watch daily: payment success rate, decline rate per bank, average transaction duration, number of support tickets. Compare against the pre-migration figures; if the success rate dropped, the cause is usually a detail in the flow, not in the rates. If you want to run collection, shipping and accounting from one place, you can look at the integration options.
Here is the job for tomorrow morning: put the number of sessions entering your payment page next to the number of successfully completed transactions and work out the gap. If that gap is above 20 percent, you have a concrete problem to fix in the payment flow before negotiating commission — and its return will be larger than the return from shaving a fraction of a point off the rate. On an e-commerce platform where payment, shipping and invoicing come connected out of the box, most of these steps start out already built.
Frequently Asked Questions
Do I have to register a company to get a virtual POS?
Yes. Payment institutions open the collection account in the name of a company or a sole proprietorship; e-commerce collection cannot run into a personal account. Applications generally ask for a tax certificate, signature circular, identification and the site address. Get the current document list from the provider before applying.
Is the commission rate negotiable?
Usually yes; rates are set according to monthly volume, sector and return rate. As your volume grows you earn the right to renegotiate. Writing volume tiers into the contract is more practical than negotiating every six months.
Can several virtual POS providers be used at once?
They can, and it is common in growing stores. There are two reasons: keeping collection alive when one provider has an outage, and routing by card to the more favourable rate. In return come two separate reconciliations and two separate reporting loads.
Is it legal to pass the instalment cost on to the customer?
Showing a term difference in the price is a widespread practice, but the total amount presented to the consumer and the term difference are expected to be stated clearly. Confirm that your implementation matches current regulation with your financial adviser.
What should my payment success rate be?
There is no universal threshold; what matters is your own trend. Most people who enter card details and press confirm are expected to complete the transaction. If the rate falls week over week, the cause is usually a change in one bank's integration or in the verification flow.
What changes if I sell abroad?
Foreign card acceptance, collection in foreign currency and cross-border dispute processes should each be asked about separately. Not every provider accepts every country's cards at the same success rate. Customs and invoicing for cross-border sales are a separate subject; a payment solution does not cover them.
Can cash on delivery replace a virtual POS?
It cannot; cash on delivery hands collection to the courier, requires post-delivery settlement and tends to raise return rates. Offering both is common, but making cash on delivery the only option worsens both cash flow and the return burden.
Will orders be interrupted while switching virtual POS?
Not when it is planned properly. The method is to validate the new provider fully in the test environment, open it in production as a second option, run both in parallel for a few days, and only then close the old one. Do not migrate during campaign periods.
Do I get the commission back when I issue a refund?
It varies by provider and contract; in some packages commission is not returned, in others it is partly returned. In categories with high return rates this clause changes total cost noticeably, so ask about it separately in the quote.
How is reconciliation data transferred to accounting?
There are two ways: downloading a file from the panel and handing it to accounting, or pulling settlement records automatically through the provider's reporting API. Once your monthly transaction count passes a few hundred, the second becomes mandatory; manual reconciliation both takes time and produces errors.