B2B E-Commerce Payment Gateways, Virtual POS and Commission Cost Analysis

Choosing a payment infrastructure for B2B e-commerce is not simply a matter of comparing the commission rates shown in provider proposals. Two solutions quoting the same rate can produce very different commercial outcomes because of settlement periods, instalment costs, payment success rates, refund processes, fixed fees and accounting workload. The consequences become more significant when a business handles high order values, customer-specific pricing, partial shipments or deferred collection.

Payment infrastructure should therefore be treated as an architectural decision spanning the entire journey from order placement and collection to ERP reconciliation—not merely as a choice between a bank and a payment service provider. The objective is not just to secure the lowest advertised rate. It is to build a secure, manageable collection model whose total cost can be measured for every order type.

What is the difference between a payment gateway and a virtual POS?

A virtual POS is a merchant solution that enables online card payments to be collected through a bank or authorised payment service provider. A business may contract with banks individually, managing each bank’s commission, settlement and instalment terms separately. Direct connections can offer greater commercial flexibility at high volumes, but they also increase responsibility for integration, certificates, error handling, reporting and ongoing operations.

A payment gateway can manage multiple banks or payment methods through a shared technical layer. Depending on its capabilities, it may route a transaction according to the card issuer, instalment choice, expected cost or real-time channel performance. A single integration can simplify operations, but service charges, per-transaction fees, contractual conditions and provider dependency must still be included in the total-cost calculation.

In Türkiye, the authorisation scope of an organisation providing payment services matters. The Central Bank of the Republic of Türkiye explains the legal framework and authorised organisations on its overview of payment services. Supplier due diligence should verify both the organisation’s current authorisation and whether the proposed services fall within that authorisation.

Why does the advertised commission rate not show the real cost?

The percentage in a proposal usually represents the variable fee for a successful transaction. The economic result of a B2B payment, however, also depends on when the money reaches the company and which additional costs arise throughout the transaction lifecycle. A reliable comparison requires every cost item to be defined and measured over the same period.

• Variable commission: Rates may vary by single payment or instalment count, card type, bank and whether the card is domestic or international.
• Fixed charges: These may include setup, monthly service, per-transaction, reporting and additional-module fees.
• Settlement cost: Receiving funds after several days instead of the next day creates a working-capital requirement.
• Refunds and cancellations: Results depend on whether commission is returned, whether partial refunds are supported and how much manual work is required.
• Failed transactions: A payment rejected by a bank or interrupted by a technical fault can become a lost order and a support burden.
• Chargebacks: Costs include not only the disputed amount but also evidence gathering, case preparation and operational time.
• Reconciliation: The effort required to match bank movements with orders, invoices and customer accounts must be included.

Consequently, the lowest commission and the lowest total collection cost are not necessarily the same. A seemingly higher rate may be more economical if it comes with faster settlement, a stronger success rate and automated reconciliation.

How should total payment collection cost be calculated?

Compare providers using a realistic monthly or quarterly transaction basket. In a simple model, total collection cost equals commissions, fixed charges, settlement financing costs, refund and chargeback losses, lost contribution from failed payments, and operational labour. Divide that amount by successfully collected volume to calculate the net cost rate.

An illustrative scenario

Consider a hypothetical B2B platform receiving TRY 5 million in monthly payment requests. Option A charges 2.20%, achieves a 92% payment success rate and settles in 14 days. Option B charges 2.45%, achieves a 96% success rate and settles in two days. Looking only at the tariff makes A appear cheaper. Once successfully collected volume, lost order contribution and the financing effect of the 12-day settlement difference are included, the outcome may reverse.

This is an analytical method, not a price estimate. A real model must use the company’s gross contribution margin, the probability that a customer will complete a rejected payment through another method, the company’s funding cost and the terms of the provider contract. All rates should also be compared on the same VAT-inclusive or VAT-exclusive basis.

Calculate a weighted commission rate

Use the actual transaction mix instead of a single headline rate. If 60% of turnover is collected in one payment, 25% in three instalments and 15% in six, multiply each category’s rate by its share of volume. Commercial and corporate card rates should be modelled separately where applicable. This prevents an attractive but rarely used rate from distorting the overall result.

How should settlement and instalment costs be assessed?

As B2B transaction values increase, even a difference of a few settlement days becomes material. Settlement cost can be calculated from the outstanding amount, the number of days and the business’s actual short-term funding rate. If a provider offers early settlement, model the associated discount or additional commission separately.

Instalments are not merely a customer convenience. The business must decide who bears the rising cost of longer terms, considering dealer group, product margin, campaign and order value. The platform should be able to disable long instalment plans for low-margin products or reflect their cost in the price. To prevent conflicts with customer-specific prices, these decisions can share a clear rule hierarchy with the platform’s special pricing and discount rules.

The cost of failed payments, refunds and chargebacks

The success rate measures the relationship between payment requests and successful collections, but it is not meaningful enough without categorising failure reasons. Insufficient funds, incorrect details, authentication failures, issuer declines, timeouts and technical outages require different responses. Essential controls include offering a secure retry path, using unique transaction keys to prevent duplicate collection and querying the provider before deciding the status of an uncertain transaction.

The refund flow should be connected to order and shipment status. For a partial shipment, only the relevant lines should be refunded after the appropriate approval, while the provider reference should be transferred to the corresponding ERP record. The physical return process can be coordinated with the RMA and warehouse-receipt lifecycle described in this guide to digitising B2B returns management.

A chargeback occurs when a cardholder disputes a transaction through their bank. Visa’s chargeback guidance notes that a request can be passed through the banking channel to the merchant’s bank. A B2B company should retain searchable order approvals, contracts, delivery evidence, user records and transaction logs. Reporting should track evidence-preparation time and missed response deadlines as well as accepted dispute values.

How should the right payment architecture be selected?

Single virtual POS

This can simplify the initial implementation where transaction variety is low and one bank dominates. Its disadvantages include the absence of an alternative channel during an outage, limited instalment coverage and dependency on a single contract.

Multiple direct bank connections

For high-volume businesses with capable finance and technical teams, multiple connections provide room for rate negotiation, bank-specific instalments and flexible routing. In return, every connection’s versions, certificates, error codes and reconciliation format must be maintained separately.

Payment gateway or hybrid model

A gateway provides shared integration and centralised reporting. A hybrid model may connect directly to strategic banks while reaching other methods through an intermediary. Its decision tree can consider customer group, issuing bank, requested instalments, transaction value, channel health and expected total cost. Automated routing should rely on measurable rules, and finance teams should be able to see why each transaction used a particular channel.

Critical points in ERP, order and finance integration

A payment record should contain more than “successful” or “failed.” Track states such as initiated, awaiting authentication, authorised, captured, cancelled, partially refunded, fully refunded and disputed. Store the order number, provider transaction ID, bank reference, instalment count, gross value, commission, net settlement and expected settlement date in a shared data model.

Webhook signatures should be verified, and repeated notifications must not create duplicate records. A timed-out request should be queried from the provider rather than automatically marked as failed. End-of-day files or API reports should be compared with orders, with amount, commission and settlement discrepancies sent to an exception queue. Matching customer-account and bank records in a controlled workflow can be treated as a continuation of the payment architecture, as outlined in this account reconciliation software guide.

Security and compliance scope

Keeping card data entirely outside the company’s systems through a hosted payment page or token-based solution can reduce security scope, but it does not remove every responsibility. The PCI Security Standards Council’s PCI DSS SAQ A guidance explains that security controls can still apply to merchant webpages in certain e-commerce scenarios using outsourced payment pages. The precise scope should be determined according to the chosen integration and an assessment by a qualified specialist.

Administration interfaces should use role-based permissions, strong authentication, tamper-resistant audit trails and masked sensitive data. Refund authority should be separated from order-approval authority, while high-value transactions may require a second approval. Logs must also be tested to ensure that personal or card data cannot leak through them.

Payment provider comparison checklist

• Weight commission rates using the real transaction mix.
• Confirm the net settlement date and early-settlement cost in writing.
• Record setup, monthly, per-transaction and minimum-commitment charges.
• Measure success rates by bank, card type and failure reason.
• Review cancellation, partial-refund and chargeback fees in the contract.
• Test outage, safe-retry and alternative-routing scenarios.
• Verify gross value, commission, net amount and settlement matching in ERP transfers.
• Clarify data ownership, export options and the provider-exit plan.

A manageable B2B payment infrastructure with Kumsal Agency

Kumsal Agency approaches payment selection as a project-specific software architecture encompassing user roles, dealer rules, the order lifecycle, security, ERP transfers and financial reconciliation—not simply as a rate comparison. Depending on real transaction scenarios and management requirements, the solution may use direct virtual POS connections, a payment gateway or a hybrid architecture.

The goal is a system in which customers can pay quickly and clearly, finance teams can monitor commissions, settlement dates and discrepancies, and technical teams can manage errors with explainable records. Contact Kumsal Agency to plan your B2B payment flows, virtual POS integrations and total commission costs around your own business rules.