Payments integration
Banka Sanal POS Paketi
What it does
- Connects your own bank virtual POS accounts to checkout through one module, covering around 15 Turkish banks.
- Runs 3D Secure payments with the bank's 3D, 3D_Pay, or 3D_Host model and verifies the return hash before an order changes.
- Applies your bank-by-card-family installment matrix at checkout, capped by the sector limits set by the regulator.
Provider based in Turkey
The Bank Virtual POS Package lets a store plug its own bank POS agreements straight into checkout. It is part of the launch catalog. Instead of one module per bank, Kambloo ships a single module built on the mews/pos library, which already abstracts the gateways used by Turkish banks: NestPay, Akbank's JSON API, Garanti GVP, Yapı Kredi Posnet, QNB PayFor, DenizBank InterPos, VakıfBank PayFlex, Kuveyt Türk, and others.
How it works with Kambloo
The module implements the standard PaymentGateway contract, so the core treats a bank POS like any PSP. The selected bank is resolved from your encrypted settings and the bank code is kept on the payment record. A payment starts with the bank's 3D form; the return is checked with mews/pos's hash verification through the central webhook endpoint. Invalid signatures are rejected. Idempotency uses the same three layers as every gateway: a lock per conversation, a unique transaction ID, and a one-way state machine.
The platform default is the 3D model. NonSecure is reserved for back-office actions such as void and refund, since 3D Secure is the practical standard in Turkish e-commerce.
Installments are the Turkish twist. Options depend on the card programme family (Bonus, World, Maximum, Axess, Paraf, CardFinans, Advantage, Bankkart Combo), not the bank alone. Kambloo resolves the BIN to a family from a seeded BIN table, reads your matrix for that bank and family, and applies your general rules: enabled counts, minimum cart amount, and surcharge handling. The regulator's sector-based maximum installment counts are seeded by the platform and updated over time; your matrix cannot exceed them, and checkout uses the strictest category in the cart.
The connection wizard walks through bank selection, credentials, a 1 TL test charge with automatic void, the matrix, and activation. Bank error codes are normalised into field-level hints. A new bank is added by a package update, not a new module.
Requirements
- A virtual POS agreement and credentials from each bank you connect.
- A passed test transaction per bank before the gateway is listed at checkout.
- Your negotiated commission rates per card family to populate the installment matrix.
Setup steps
The short version. The screens in your store admin follow the same order.
- Install the Bank Virtual POS module from the Market. It is free. One module covers all supported banks.
- Open the connection wizard and pick a bank. The form shows the credential fields that bank needs.
- Enter test or live credentials. The wizard runs a 1 TL 3D Secure charge and voids it. The gateway is not listed at checkout until this test passes.
- Fill in the installment matrix: bank, card family, installment count, commission, and optional surcharge.
- Activate. You can repeat the wizard to connect more than one bank.
Questions about Banka Sanal POS Paketi
Which banks are supported?
The design list covers Akbank, İş Bankası, Ziraat, Halkbank, TEB, Şekerbank, Garanti BBVA, Yapı Kredi, Albaraka, QNB, Ziraat Katılım, DenizBank, VakıfBank, Kuveyt Türk, Vakıf Katılım, and Emlak Katılım. Each bank is confirmed against its current integration document before it goes live.
Why would I use this instead of iyzico or PayTR?
Commission. A merchant with its own bank agreement usually pays noticeably less per transaction than through a PSP. The trade-off is a bank application process and a manually entered installment matrix.
Can I connect several banks at once?
Yes. If more than one POS is active, Kambloo prefers the bank whose card programme matches the customer's card family. Otherwise it uses your default POS.