Payments integration
Craftgate
What it does
- Routes each payment to one of several bank virtual POS accounts or PSPs through a single integration.
- Fails over to a backup POS when the primary one is down, without a change on your side.
- Keeps stored cards in a shared vault so one token works across every POS behind Craftgate.
Provider based in Turkey
Craftgate is a payment orchestration layer. It is part of Kambloo's launch catalog, alongside Stripe and the bank virtual POS package. Stores that hold contracts with several banks and want the lowest-commission route per transaction are the target. The adapter is an Internal Module.
How it works with Kambloo
To the Kambloo core, Craftgate is an ordinary gateway. It implements the same PaymentGateway contract as iyzico and PayTR: start a payment, verify the callback, query status, refund, and return installment options. The checkout does not know that several bank accounts sit behind it.
The value is on the Craftgate side. You register your bank POS accounts there and define rules. For each payment Craftgate can send the transaction to the POS with the lowest commission for that card, and switch to a backup when a POS fails. Kambloo receives one signed callback per payment through the central webhook endpoint, checks the signature, and applies the same idempotency rules as for every other gateway: a cache lock per conversation, a unique transaction ID, and a one-way state machine.
Installments are returned by Craftgate per BIN and amount, so the checkout shows a live table without a manually maintained matrix. Stored cards live in Craftgate's shared vault. A card saved once can be charged through any POS behind the orchestration, and Kambloo keeps only the token and masked metadata.
Shopping credit and buy-now-pay-later options are on Kambloo's post-launch expansion queue, not in the launch catalog. Craftgate connects to providers such as ZIP, TOM Finans, and Hepsipay Shopping Credit with one integration, which is why Kambloo routes those methods through Craftgate rather than building each one.
Requirements
- A Craftgate account with at least one connected bank POS or PSP.
- Craftgate API credentials, stored encrypted in your store settings.
- Installment agreements are configured with your banks; Craftgate reports them to Kambloo at checkout.
Setup steps
The short version. The screens in your store admin follow the same order.
- Install the Craftgate module from the Market. It is free.
- Enter your Craftgate API key and secret under Settings > Payments > Craftgate.
- Connect your bank POS accounts and routing rules inside your Craftgate panel.
- Place a 3D Secure test order and check the result in the payment log.
- Enable the gateway for checkout.
Questions about Craftgate
How is Craftgate different from connecting a bank POS directly?
A direct bank POS is one bank, one contract, and a manual installment matrix. Craftgate sits in front of several POS accounts and picks the best one per transaction. It adds a technology layer and a fee for that service.
Does Kambloo do the smart routing itself?
No. Kambloo's own multi-POS logic is simple: prefer the bank that matches the card family, otherwise use the default. Routing and failover across many POS accounts is Craftgate's job.
Does Craftgate cover shopping credit and BNPL?
Not at launch. Shopping credit and BNPL sit on Kambloo's post-launch expansion queue. Because Craftgate offers one integration to several shopping-credit providers, that queue routes those methods through this module rather than separate adapters.