Card Providers
Accept card payments through connected bank virtual POS systems or payment institutions. Select a provider in POS Center → Discover and enter your account’s connection details in the panel.
| Provider | Connection type |
|---|---|
| Akbank | Bank virtual POS |
| DenizBank | Bank virtual POS |
| Garanti BBVA | Bank virtual POS |
| Halkbank | Bank virtual POS |
| İş Bankası | Bank virtual POS |
| QNB Finansbank (NestPay) | Bank virtual POS |
| QNB Finansbank (PayFor) | Bank virtual POS |
| VakıfBank | Bank virtual POS |
| Yapı Kredi | Bank virtual POS |
| Ziraat Bankası (Payten) | Bank virtual POS |
| Ziraat Bankası (PayFlex) | Bank virtual POS |
| iyzico | Payment institution / PSP |
| Moka | Payment institution / PSP |
| Paycell | Payment institution / PSP |
| Paynkolay | Payment institution / PSP |
| PayTR | Payment institution / PSP |
| QNBpay | Payment institution / PSP |
| Rubik Para | Payment institution / PSP |
| TKPAY | Payment institution / PSP |
Payout schedule and transaction matching
Under POS Center → Your connection → Payout & Reconciliation, select the Provider response schedule when your provider supports it. This is the default for QNBpay connections; an existing manual schedule is preserved. With Provider response (API) reconciliation, Lunixi matches transactions processed through Lunixi against the provider's authenticated response.
The provider-reported payout date appears on the transaction row. A missing date remains pending; Lunixi does not assume T+1. Neither this date nor a successful transaction match confirms that funds have reached your bank account.
When you use your own POS connection, the provider pays your account according to your agreement. The gross capture is not recorded as a platform balance payable to you by Lunixi.
QNBpay matching uses per-transaction status inquiries. It is not a complete statement of your QNBpay account or confirmation of a bank transfer.
QNBpay connects with an App Key, App Secret and Merchant Key; it supports card payments, 3D Secure and refunds according to your account permissions, with commission and active-installment information available on the connection screen.
To receive QNBpay server notifications, register these URLs in the API settings of your QNBpay merchant portal. Enter each portal-generated key in the corresponding QNBpay sale notification key or QNBpay refund notification key field of your Lunixi connection. These optional fields do not replace App Key or App Secret.
| Notification | URL to register in QNBpay |
|---|---|
| Sale | https://api-gateway.lunixi.com/api/v1/provider-callbacks/qnbpay/sale |
| Refund | https://api-gateway.lunixi.com/api/v1/provider-callbacks/qnbpay/refund |
Ask QNBpay to enable any firewall permission required for delivery to these URLs. These addresses receive QNBpay notifications in Lunixi; they are separate from the customer's browser return URL and the Lunixi webhook URL in your own application.
A refund response with code 101 means the request has been queued. Receiving a notification alone does not confirm refund completion. If the provider supplies no reference that verifies the individual refund, Lunixi does not infer its result from the sale's cumulative refunded amount; transaction-specific confirmation from QNBpay is required.
Installments and operation permissions depend on the provider and your merchant agreement. Use Card Payments, Installments & BIN and Refunds for the shared request and response contracts.
PayTR
PayTR connects with a Merchant ID, Merchant Key and Merchant Salt. Find them in the PayTR Merchant Panel under Destek & Kurulum → Entegrasyon Bilgileri (Support & Setup → Integration Information). Card details are collected in the Lunixi payment form; PayTR’s own payment page is not used.
Before connecting, confirm that the following permissions are enabled on your PayTR merchant account. You can request them from PayTR.
| PayTR permission | Required for |
|---|---|
| Direct API | Card payments and 3D Secure |
| Non3D | Card payments without 3D Secure |
Without the Non3D permission you can accept 3D Secure payments only.
Notification URL
PayTR reports the payment result server to server and does not complete a payment until the notification is acknowledged. In the PayTR Merchant Panel, enter the URL below under Ayarlar → Bildirim URL Ayarları (Settings → Notification URL Settings) and select HTTPS as the protocol.
| Notification | URL to register in PayTR |
|---|---|
| Payment result | https://api-gateway.lunixi.com/api/v1/provider-callbacks/paytr/notification |
PayTR accepts a single notification URL per merchant account. If the same account is also used on another site, that site’s notifications arrive at this URL too and are not processed by Lunixi; use a separate PayTR merchant account for your Lunixi connection.
This address receives PayTR notifications in Lunixi; it is separate from the customer's browser return URL and the Lunixi webhook URL in your own application.
Payments, installments and refunds
- The payment result is verified through PayTR’s notification and status inquiry. The customer reaching the return page does not by itself mean the payment has completed.
- If the customer does not complete 3D Secure authentication, the payment is closed as failed after the session expires.
- Single payments and 2–12 installments are supported. Installments depend on the card’s card program and your PayTR agreement; cards that belong to no card program cannot be charged in installments. Installment rates reported by PayTR are shown on the connection screen.
- You can accept payments in TRY, USD and EUR. USD and EUR require approval from PayTR.
- Full and partial refunds are supported. A refund is carried out when your net balance at PayTR is sufficient.
- Pre-authorization and void are not available on PayTR connections. Use a refund to reverse a payment on the same day.
If passing the installment surcharge on to the customer is enabled in the PayTR Merchant Panel, the customer is charged an amount different from the one they approved. Lunixi does not treat such a payment as completed and places the transaction under reconciliation review. Keep this setting disabled for installment sales.
Testing
While the Test Mode option of the connection is enabled, transactions are sent to PayTR as test transactions and no real charge is made. PayTR has no separate test environment; test and live transactions use the same merchant credentials. For test cards, see PayTR’s test card details (opens in a new tab) page.
TKPAY
Create your connection under POS Center → Discover → TKPAY. Enter the Merchant ID, Store Key, API Username, API Password, Client ID and Client Secret supplied by TKPAY. Your TKPAY API username is separate from your Lunixi panel login.
Use a TKPAY sandbox account for a test connection. The outbound IP address for each environment must be allowlisted by TKPAY. Live payments require TKPAY’s live account and endpoint; test credentials do not collect real funds.
Payments and installments
- Card payments support TRY, USD, EUR and GBP. Include the customer's phone number, email and IP address in the payment request.
- In the standard Lunixi card flow, Lunixi completes the payment after 3D Secure authentication and queries its result server to server. A successful browser return alone does not prove capture.
- Non-3D sales require the relevant TKPAY account permission. A transaction requiring 3D Secure is never automatically downgraded to 2D.
- Installments are queried for the first eight card digits, amount, currency and connection. The technical maximum is 36 installments; available options depend on the card and your TKPAY agreement.
- The approved customer total is preserved. If TKPAY quotes a different total for the selected installment, that connection is ineligible for the approved total.
- The TKPAY connection reads commission from transaction reports. This commission belongs to the individual transaction; it does not automatically update your cost table or customer installment rate.
Refunds and cancellation
Full and partial refunds are supported. Multiple partial refunds cannot exceed the original sale, and TKPAY requires sufficient unpaid settlement balance. Cancellation is available on the same day before the provider closes its batch. A rejected cancellation does not automatically trigger a refund.
A sale or refund with a lost response is not blindly resent. Inquiry and transaction reports are used to check the result. If the provider cannot identify an individual refund operation, it remains pending; cumulative refunded value does not prove that a particular refund completed.
Payout and reconciliation
Under Payout & Reconciliation, use Provider response (API) matching and the Provider response schedule. An existing manual schedule is preserved.
Transaction reports include sales, refunds and cancellations, with the amount, commission and payout date when supplied. A provider-paid flag appears as Provider reports paid · bank confirmation pending. It does not replace matching a bank statement. Missing commission or dates are not filled with zero or an assumed next-day date.
With your own TKPAY POS, settlement is between TKPAY and your business. Lunixi does not record gross collections as platform funds payable to you.
Return URLs
TKPAY browser returns use the address Lunixi supplies when initiating payment. You do not need to register a separate sale/refund webhook URL in TKPAY. Configure the Lunixi webhooks sent to your application separately.