Skip to content
7 min read

Connect Payme to Website: Documents, Timeline, Click and Testing

If you want to connect Payme to a website, start with documents and site pages rather than code: they decide whether you pass moderation. Online payment removes the weakest moment of a sale, the request to 'transfer to this card and send a receipt', where some buyers simply leave. Below you will find what to prepare, the order of steps, how data is exchanged with the payment service, how to test everything and which mistakes are the most common. Click is covered alongside, because a shop almost always needs both methods.

What you need before you start

Payment services sign contracts with registered companies and sole traders, so an individual without business registration usually cannot connect. Prepare registration documents, bank account details, a description of your activities and a contact person. Check the exact document list and application form with the service you choose, because requirements can change.

The second condition is a finished site. It must run on HTTPS and contain what a moderator checks: a description of goods or services with prices, a public offer agreement, payment, delivery and refund terms, real contacts and company details. A placeholder instead of a catalogue, or a payment page with unclear terms, is the most common reason for rejection.

A checklist before you apply: the HTTPS certificate is valid; the catalogue shows prices in sums; the offer and refund terms are reachable from the footer; phone, address and legal entity name are listed; every item has a clear description; a test checkout runs through to the end.

How to connect Payme to a website: step-by-step plan

Step one is the application and contract: you send documents, give the site address and receive access to the merchant account. Step two is getting integration data: a cash register identifier and secret keys for the test and live environments. Keep keys on the server only, in environment variables, and never put them in page code or a public repository.

Step three is development. The site creates an order in the database with the status 'awaiting payment' and builds a payment link with the amount and order number. After that the payment service contacts your server at a pre-agreed address. With Payme these are JSON-RPC requests: checking whether payment is possible, creating a transaction, confirming, cancelling and a statement. Payme passes amounts in tiyin, hundredths of a sum: an order of 100,000 sum is 10,000,000 tiyin. This mix-up is forgotten more often than you would think.

Step four is the test environment, step five is the service's own check and the switch to live keys. Leave a time buffer: the service itself states how long it takes to review an application. As a guideline, building the integration on a site that already has order logic takes from a few days to a couple of weeks.

How the payment flow works and why the server sets the status

The flow is this: the buyer clicks 'Pay', the site sends them to the payment service's page, and they enter card details there, not on your site. So card details never reach your server and you do not have to store them. After payment the service sends a notification to your server and returns the buyer to the thank-you page.

Order status must change only on the server notification. A browser redirect can be faked, it does not happen if the tab is closed or the connection drops, while a service-to-server request with signature or key verification cannot be faked. The thank-you page only displays the order state from the database and decides nothing.

Check every incoming request: is the signature or authorisation valid, does the order exist, does the amount match the one calculated on the server, is the order already paid. Reply in the format the service requires, otherwise the operation will be treated as failed.

Click, fees and settlement times

Click connects on the same principle, but the exchange differs: the service sends two requests, prepare and complete, and each carries a signature you must verify. Order logic stays yours, so build a shared 'order and payment' layer straight away and plug both services into it instead of writing two separate solutions.

Fees depend on turnover, line of business and the contract, and there are no universal figures. Request terms in writing from each service and calculate what you would pay at your average order value. Also ask how many business days it takes for money to reach your bank account and how refunds are handled. A shop usually needs two online methods plus payment on receipt: if the buyer's familiar app is missing on the payment page, they leave without ordering.

Testing and common mistakes

Test more than a successful payment. The minimum scenarios: enough funds, insufficient funds, cancelling on the payment page, closing the tab midway, a repeated notification for the same order, paying an already paid order, full and partial refunds, and a wrong amount. These are exactly the cases that surface on a live site and spoil your reporting.

Frequent mistakes: the browser calculates the total instead of the server; no idempotency, so a repeated notification creates a second paid order; keys sit in page code; status changes when the buyer returns; there is no log of the service's requests; a refund is made in the merchant account while the order on the site stays paid. Keep a log with order number, time, request type, amount and response. It helps when reconciling against the statement.

FAQ

Can I connect Payme to a website without a registered company? Usually not: services sign contracts with legal entities and sole traders. Check current conditions with the service itself.

How long does connecting take? Development with ready order logic takes from a few days to a couple of weeks, while the service tells you how long the application review takes. So submit documents early.

Do I need both Payme and Click? Not necessarily, but two methods reduce the risk of losing a buyer who has the other app at hand.

Does the site store card data? No, the card is entered on the payment service's page and your server only receives the result of the operation.

Can I add payments to a site built on a website builder? It depends on the builder: it must be able to receive server requests and store orders, otherwise a separate server module is needed.

What affects the price and where to start

The price is made up of order and cart logic (if you have none), integration with each service, testing, refunds and a section for viewing payments. As a market guideline for Uzbekistan, connecting one service to a ready site costs roughly 1,500,000 to 6,000,000 sum; an online shop from scratch costs more and depends on the catalogue. This is only a guideline, the final figure depends on the task.

If the site does not exist yet, build payment into the project from the start. At 4 Digital, turnkey website creation starts from 1,399,000 sum, and we discuss online payment at the beginning together with the catalogue structure, so that orders do not have to be rebuilt later.

Need a website or ads? Let’s discuss your project.

Turnkey Website Development + CRM · от 2 399000 сум

We reply within 15 minutes during business hours. No spam.