Skip to main content

Payment Methods

Payment methods are configured and assigned to stores. Each store can have different payment providers enabled.

Managing Payment Methods​

Navigate to Settings → Payment Methods.

Editing a payment method​

Choose the payment gateway from the list. The settings form is built from what that gateway needs (keys, test mode, …), with required fields marked. Saved keys are never shown again: the field reads Saved — type to replace, and leaving it empty keeps the stored key. For gateways that send notifications (Payten), the form shows the notification address to register in the gateway's panel, with a copy button.

Gateways the API does not describe (EstPOS, Stripe) appear as Other: enter the provider key and the configuration as JSON.

An enabled method is checked when saved: missing or invalid settings are refused with the reason.

Supported Providers​

Stripe​

Global payment processor supporting credit/debit cards, Apple Pay, Google Pay.

Configuration:

  • API Secret Key (from Stripe Dashboard)
  • Webhook endpoint for async payment confirmations

Iyzico​

Turkish payment processor supporting local cards, installments, and BKM Express. Provider key iyzico. The shopper pays on iyzico's hosted Checkout Form, so card data never reaches your store. Installment options are those enabled in your iyzico merchant panel.

Configuration:

  • API Key and Secret Key (from the iyzico merchant panel; sandbox keys from sandbox-merchant.iyzipay.com)
  • Sandbox: on for test keys, which use sandbox-api.iyzipay.com

Keys are never shown again after saving: the form displays ********, and saving the mask unchanged keeps the stored key.

Payten Payment Gateway​

Provider key payten. Payten (MerchantSafe Unipay) routes each payment to one of your own bank virtual POSes: the cheapest by your rules, or a fallback when one is down. Installments and 3-D Secure are set up in the Payten panel. The shopper pays on Payten's hosted page, so card data never reaches your store.

Configuration:

  • Merchant (business id), API user (e-mail) and API password, from the Payten panel
  • Secret key: the merchant secret from the Payten panel, which verifies payment results and notifications
  • Test environment: on for test credentials (test.merchantsafeunipay.com)
  • Payment system (optional): forces one POS; leave empty to let Payten route

In the Payten panel, under Settings → Profile → Financial Transaction Notifications, register the notification address https://<your-api>/api/storefront/payments/notify/<payment method id>. Notifications settle payments whose shopper closed the page before returning to your store.

Bank transfer (Havale / EFT)​

Provider key bank_transfer. The order is created at once as awaiting payment, and the shopper sees your account details: bank, account holder, IBAN (required), plus optional SWIFT/BIC, account number, branch code and description. Mark the order paid when the money arrives.

EstPOS (Turkish Bank Virtual POS)​

Direct bank virtual POS integration (EST v3 gateway, provider key tr_est_v3) for Turkish acquiring banks such as Akbank, Yapı Kredi, and others on the EST platform. Supports 3D Secure card payments.

Configuration:

  • Bank Code (which EST bank endpoint to use)
  • Client ID (merchant / terminal ID from the bank)
  • Store Key (3D Secure hashing key from the bank)
  • Username & Password (API credentials from the bank)

Store Assignment​

Payment methods are assigned per store:

  1. Edit a store in Settings → Stores
  2. Select which payment methods are available for that store

During checkout, only the payment methods assigned to the customer's store are presented.

Payment Flow​

info

Adding a new payment provider requires backend development (new payment provider implementation). The Backoffice manages configuration and store assignment for existing providers.