Tarlan Payments

Tarlan Payments Overview For Merchants

If you sell to customers in Kazakhstan and need a PCI DSS compliant gateway with documented APIs, Tarlan Payments is a local payment organization that provides card acquiring, Apple Pay and Google Pay acceptance, payouts, and integration options ranging from hosted forms to direct API. Tarlan Payments publishes developer documentation that covers payment flows, 3D Secure, webhooks, and fiscal receipt retrieval, which helps you evaluate technical fit and compliance from day one.

What Is Tarlan Payments

Tarlan Payments is a Kazakhstan payment organization and payment gateway that enables you to accept online card payments and digital wallets, initiate payouts, and manage transactions through an API and merchant cabinet. The public docs describe one stage and two stage flows, tokenization for one click payments, and wallet acceptance. Tarlan Payments states in its documentation that it is PCI DSS compliant and supports both 3DS 1.0 and 3DS 2.0. It appears in the National Bank of Kazakhstan register of payment organizations, which signals local regulatory oversight.

Tarlan Payments Products And Capabilities

Card Payments With 3D Secure

You can process internet acquiring with 3DS authentication. The developer docs explicitly note support for 3DS 1.0 and 3DS 2.0, which is important for SCA, fraud reduction, and issuer liability shift. Transaction status codes and error codes are documented to help you handle edge cases and declines.

One Stage And Two Stage Flows

Tarlan Payments documents both:

• One stage payment – authorization and capture happen in a single step.

• Two stage payment – you authorize funds first, then confirm capture or cancel later.

This split is useful when you ship later or need to verify inventory before final capture.

Stored Cards And One Click

A card-linking flow issues a payment token that can be reused, enabling one click payments without re-entering card details. Tokenized storage helps lower checkout friction for returning customers while keeping sensitive PAN data off your systems.

Apple Pay And Google Pay

• Apple Pay – a documented endpoint is provided for creating Apple Pay transactions. The docs clarify that Apple Pay on the web flow is available on iOS.

• Google Pay – the documentation points to Web integration, with references to Google’s merchant registration and branding rules.

These wallet options help lift mobile conversion and reduce keying errors.

Payouts

For marketplace or wallet use cases, you can initiate payouts via API. This is helpful for refunds that require pushing funds or for disbursements to your partners or contractors.

Integration Options

Hosted Form And Iframe

In addition to server side APIs, there is an Iframe option for presenting a hosted payment form. Hosted forms reduce PCI scope because card data is handled by the PSP.

Direct API

REST JSON endpoints are documented for creating transactions, checking statuses, confirming or canceling captures, issuing refunds, creating payment links, and more. Signatures and headers are documented, which simplifies signing and verification on your side.

CMS Integrations

If you run a site on a CMS, the docs include integration guides for:

• WordPress and WooCommerce – widget based integration, with notes about localization and wallet support.

• Bitrix – instructions for adding the gateway.

• Tilda – connection steps specify entering Merchant Project ID and Secret Key, with currency selection showing Kazakhstan tenge (KZT).

These options allow you to start quickly without writing a custom checkout.

Payment Links

You can generate hosted payment links through an API method. This is useful for invoicing, support mediated payments, or quick one off collections without a full checkout.

Webhooks

Payment status webhooks are documented, including events for payment readiness and final status. Webhooks are essential for reconciling asynchronous results, 3DS completion, and wallet flows.

Fiscalization Support

For Kazakhstan fiscal rules, the docs include a method to retrieve a fiscal number and receipt by payment identifier. If you need to issue fiscal receipts, this endpoint is a key compliance component.

Security And Compliance

• PCI DSS – the PSP’s documentation explains PCI DSS expectations and states that Tarlan Payments annually passes certification and complies with the requirements. Offloading card entry to their hosted form or wallet flows helps keep cardholder data out of your environment.

• 3D Secure – both 3DS 1.0 and 2.0 are supported, which improves authentication rates and decreases issuer related fraud chargebacks.

• Tokenization and Encryption – flows for card encryption and payment tokens are described, enabling one click payments without storing raw PAN data on your servers.

Currencies, Geography, And Local Considerations

• Currency – the Tilda integration guide shows currency selection as KZT. If you require additional currencies or settlement options, request confirmation from the provider because only KZT is explicitly shown in the public CMS guide.

• Regulatory Status – Tarlan Payments is listed in the National Bank of Kazakhstan’s register of payment organizations. This status is relevant for merchants that must work with locally registered PSPs.

Merchant Operations And Reporting

• Merchant Cabinet – you are issued a merchant ID and receive access to a cabinet for operational control and reporting.

• Statuses And Errors – transaction statuses and error codes are documented, which lets you map outcomes to customer messaging and support playbooks.

• Refunds, Captures, Voids – there are explicit methods for refund, capture confirmation, and canceling holds, which you can wire into your OMS or customer portal.

When Tarlan Payments Fits Your Use Case

Choose Tarlan Payments if you need:

• A locally registered PSP for Kazakhstan with published technical documentation and PCI DSS compliance.

• 3DS authenticated card payments with the option to run two stage flows.

• Apple Pay and Google Pay on the web to improve mobile conversion.

• A fast start through WordPress, Bitrix, or Tilda integrations while retaining the option to migrate to direct API later.

• Fiscal receipt retrieval and webhook events to keep your ERP, CRM, or cash register in sync.