Tuqo + YooKassa
YooKassa is one of the most popular payment providers in Russia. With a static site on Tuqo, the easiest way is ready-made payment links and invoices plus the embeddable widget: they need no backend of your own. Tuqo serves static files and runs no server code, so payments go through YooKassa's own tools, and the provider itself issues the fiscal receipt required by Russian law 54-FZ.
What Tuqo + YooKassa gives you
- Payment links and invoices: payment with no code and no server
- A ready-made payment widget or form on the site
- One-time payments and subscriptions
- 54-FZ receipts via YooKassa's cloud fiscalization, no cash register of your own
Connect YooKassa
Register a shop (you need a sole proprietorship or a company registered in Russia) and get the shopId and the secret key in the dashboard.
The simple path: a payment link
Create an invoice or a payment link in the YooKassa dashboard and put it on the site as a button. No code, no backend; YooKassa issues the receipt.
Or the embeddable widget
Use YooKassa's ready-made payment form or widget: the payment happens on the provider's side in a secure window.
Production and confirmation
Reliable payment confirmation and subscriptions need server-side webhooks. On a static site that means an edge function (planned at Tuqo) or YooKassa's cloud tools.
<!-- A YooKassa payment link: an ordinary button, no code, no backend -->
<a href="https://yookassa.ru/my/i/XXXXXXXX/A" class="pay-button">
Pay 1000 ₽
</a>
<!-- The full YooKassa API (creating a payment with shopId + secret) runs
ONLY on a server, never in a static site. -->Security
The YooKassa secret key (and the shopId with the secret for the API) belongs ONLY on a server; never put them in a static site. On a static site, use payment links, invoices and the ready-made widget, which need no secret. The full API (creating payments, handling webhooks) is server-side; on Tuqo that will be a future edge function, or you use the provider's own cloud tools. Under 54-FZ a receipt is mandatory: YooKassa offers cloud fiscalization, and with payment links the receipt is on its side.
Tuqo serves the front end over HTTPS and never touches your data or the service's secrets.
Tuqo + YooKassa — frequently asked questions
Can I take payments without a backend of my own? +
Yes, with YooKassa payment links, invoices and the widget: the payment happens on the provider's side. Reliable confirmation and subscriptions need a server (webhooks).
What about 54-FZ receipts? +
A fiscal receipt is mandatory under Russian law. YooKassa offers cloud fiscalization, so you don't buy a cash register; with payment links, fiscalization is on YooKassa's side.
Where do I keep the secret key? +
Never in a static site. Only on a server: the full YooKassa API is server-side, and on Tuqo that will be a future edge function.
How is this different from the “Payments in Russia” page? +
This page covers YooKassa on its own. An overview of all Russian providers (YooKassa, CloudPayments, T-Bank) is on the “Payments in Russia” page.