Reference

Read this documentation: generate RSA keys (see "Key generation" section), then create an API key in your Finik personal account. For individual entrepreneurs — everything is done through the app and personal account. For organizations — contact Finik representatives, they will help you at every step.

First generate RSA keys using the openssl commands (see "Key generation" section). Then log in to your Finik personal account, open the "Keys" section and click "Generate key" — provide your public key and select type WEB. Done: you will receive an x-api-key for integration.

The beta environment is used for debugging the integration — you can create payments without real money being charged. The production environment works with real funds. Separate API keys are issued for each environment: beta — https://beta.api.acquiring.averspay.kg/v1/payment, prod — https://api.acquiring.averspay.kg/v1/payment.

Check the following:

Whether the API key is used for the correct environment (beta or production). A common cause is using a beta API key in production or vice versa. Whether the API key was copied correctly. A few characters at the beginning or end of the key may have been accidentally missed when copying. Make sure an up-to-date and valid API key is being used.

In most cases, the error is related to using the wrong API key or copying it incorrectly.

A Callback URL is the address of your server to which we send POST notifications about payment status (success/error). This is optional but recommended for automation. You can specify it when sending your public key or add it later through your personal account. The notification format is described in the documentation.

Check that your server is accessible from the outside, supports HTTPS, and accepts POST requests. Also make sure you have correctly specified the Callback URL in the settings (no errors in the domain). If everything is correct — check your server logs and contact us to verify notification delivery.

No, each merchant must have their own unique public key. A separate key pair is generated for each legal entity or individual entrepreneur. This is a security requirement.

No, in the beta environment no top-up is required as payments do not charge real funds. However, if you use the production environment for testing, you need to top up your account as real money is charged (transaction fees apply).

Required fields: CardType (always FINIK_QR), PaymentId (unique UUID), RedirectUrl, and the Data object with accountId, name_en, and webhookUrl. The Amount field is optional — if not provided, the client enters the amount themselves. See the "Request body" section for details.

Conduct a test payment for a minimum amount (e.g., 0.01 som) in the beta environment. If you receive a successful response, see the transaction in your personal account (if you have access), and also receive a notification to your Callback URL (if configured) — the integration is working.