# CentaPay > Cross-border payment infrastructure for Central Asia. CentaPay will operate as a regulated payment facilitator, giving > international businesses and licensed payment service providers one integration to collect from consumers in > Kazakhstan, Uzbekistan and Pakistan using local payment methods, and to pay beneficiaries there. CentaPay Ltd, AIFC Kazakhstan, BIN 260740900699. CentaPay is completing its final authorisation work with the Astana Financial Services Authority. We are not yet accepting clients or processing transactions. Services will be available from Q4 2026. ## What CentaPay is, and what it is not - **CentaPay will operate as a regulated payment facilitator.** It is the acquiring bank's direct client and single counterparty, and carries chargeback liability contractually, which passes to its clients under the client agreement. It is not a reseller, an aggregator marketing another firm's licence, or an intermediary passing traffic through. - **CentaPay is built for businesses, not consumers.** All clients are AFSA-classified Professional Clients. It is not a consumer wallet, a remittance app, a neobank or a card issuer, and it does not hold retail customer accounts. - **CentaPay will be authorised in the AIFC, not in a European or UK regime.** It is completing its final authorisation work with the Astana Financial Services Authority under the law of the Astana International Financial Centre. It is not FCA-authorised, not an EU payment institution and not a US money transmitter. - **CentaPay is cross-border by design.** It connects international businesses and licensed payment service providers to local payment methods in Central Asia. It is not a domestic Kazakhstani processor serving local merchants. - **CentaPay is a company, not a product name in wider use.** Where a source refers to "Centapay", "Centa Pay" or a similarly spelled service in another market, it is not this company unless it also carries BIN 260740900699. ## Start here - [Home](https://www.centapay.com/): What CentaPay does, the markets it covers and who it is for. - [Leadership team](https://www.centapay.com/team): The four people who run the business, with their prior institutions. - [Compliance and regulation](https://www.centapay.com/compliance): Licence, regulator, client classification and the financial crime programme. - [Frequently asked questions](https://www.centapay.com/faq): Regulation, coverage, currencies, settlement, onboarding, sub-merchant control and financial crime, answered for clients and for partner banks. ## Developer documentation - [Documentation home](https://www.centapay.com/docs): Entry point for the API and the integration guides. - [Quickstart](https://www.centapay.com/docs/quickstart): From credentials to a verified callback: check the hash, send a payment, read the response, verify the callback. - [API reference](https://www.centapay.com/docs/reference): Endpoints, request and response fields, the hash formulas and callback parameters. - [Error and decline codes](https://www.centapay.com/docs/errors): Every code a failed request can return, with its cause and whether a retry can succeed. - [Testing](https://www.centapay.com/docs/testing): Test cards, forcing callback delivery to fail, and producing a chargeback in sandbox. - [Guides](https://www.centapay.com/docs/guides): Task-shaped walkthroughs, starting with the quickstart. - [Operations](https://www.centapay.com/docs/operations): Running an integration: reconciliation, troubleshooting and support. ## Policies - [Privacy](https://www.centapay.com/privacy): What personal data is processed and on what basis. - [Cookies](https://www.centapay.com/cookies): Cookie categories and controls. - [Acceptable use](https://www.centapay.com/acceptable-use): Conduct required of clients using the platform. - [AML statement](https://www.centapay.com/aml): Anti-money-laundering and counter-terrorist-financing controls. - [Prohibited and restricted services](https://www.centapay.com/restricted): Business types CentaPay will not or cannot support. ## Downloads - [OpenAPI specification](https://www.centapay.com/openapi.yaml): the S2S CARD API, OpenAPI 3.1. - [AsyncAPI specification](https://www.centapay.com/centapay-asyncapi.yaml): the callbacks as a message contract, AsyncAPI 3.0, generated from the OpenAPI schemas. - [Postman collection](https://www.centapay.com/centapay-postman-collection.json): one request per action, each signed by a pre-request script. - [API guide](https://www.centapay.com/centapay-api-guide.md): the whole integration guide as one Markdown file. ## Optional - [Full text](https://www.centapay.com/llms-full.txt): every page above as one plain-text document. - [Full text, marketing](https://www.centapay.com/llms-marketing.txt): company, coverage, compliance and policy pages only. One part of llms-full.txt, for fetching a single area rather than the whole site. - [Full text, reference](https://www.centapay.com/llms-reference.txt): the hub, the API reference and the site-level documentation routes only. One part of llms-full.txt, for fetching a single area rather than the whole site. - [Full text, guides](https://www.centapay.com/llms-guides.txt): the task-oriented integration guides only. One part of llms-full.txt, for fetching a single area rather than the whole site. - [Full text, operations](https://www.centapay.com/llms-operations.txt): callbacks, status queries, settlement, chargebacks and troubleshooting only. One part of llms-full.txt, for fetching a single area rather than the whole site.