Stripe

Stripe is Kambloo's gateway for cross-border sales. It is part of the launch catalog. Its scope is narrow on purpose: Stripe does not serve companies resident in Turkey, so the adapter is meant for merchants who sell abroad through a company registered elsewhere. The module is an Internal Module with no fee from Kambloo.

How it works with Kambloo#

Stripe implements the same PaymentGateway contract as every other card gateway. Checkout starts a payment, Stripe handles authentication, and a signed webhook event tells Kambloo the outcome. The webhook lands on the store's central endpoint, where the signature is verified before the payload is stored and handed to a queue job. Duplicate events are caught by a unique event ID, and the payment state machine prevents a captured payment from being processed twice.

Authentication follows Stripe's SCA flow. When the issuing bank requires it, the customer completes 3D Secure 2 on Stripe's side. Kambloo's servers never receive the card number, which keeps PCI scope at SAQ-A. If Stripe's confirmation does not arrive within 10 minutes, a status query job resolves the payment so the order does not stay pending.

Card storage uses Stripe PaymentMethods. Kambloo keeps the PaymentMethod identifier, the brand, and the last four digits. A saved card can be charged for a repeat purchase; if the bank asks for authentication again, the customer is sent through the normal 3D Secure step. Deleting a card in the customer account also detaches it at Stripe.

Installments are not offered through Stripe. The adapter reports that it does not support them, so the checkout shows a single payment amount. Refunds, partial or full, go through Stripe's refund API from the order screen. Per-currency price lists are a separate storefront feature; this page covers collection through Stripe.

Requirements#

• A Stripe account owned by a company registered outside Turkey.
• Stripe secret key and webhook signing secret.
• A live store domain reachable by Stripe's webhook delivery.