Online payments
Cards, SBP, Pay services and pay-in-installments, all under a single balance.
- Authorization and capture in one call
- Pre-authorization, partial capture and refunds
- Automatic retries on soft declines
CentralGatePay is the payment infrastructure behind fast-growing businesses in Russia. Accept Mir cards, SBP and Pay services through a single integration, with smart routing, built-in fraud defense and settlement you can actually plan around.
Accept:
Mir SBP SberPay T-Pay Mir Pay Dolyame Visa and Mastercard by Russian banksAcquiring, routing, risk and payouts run on the same platform. One contract, one dashboard, one reconciliation file, no matter how many methods you accept.
Cards, SBP, Pay services and pay-in-installments, all under a single balance.
Launch a ready-made checkout in minutes, hosted by us or embedded in your site.
Recurring billing with retry logic that keeps churn from eating your revenue.
Marketplaces and platforms split every transaction between sellers automatically.
A risk engine trained on network-wide signals, tuned to your own approval targets.
Money reaches your bank account on a schedule you choose.
54-FZ fiscal receipts, handled automatically. Our cloud cash register issues each receipt and sends it to the customer by email or SMS. No cash register of your own required.
This is a sandbox simulation of the CentralGatePay authorization flow. Pick a payment method, run the payment and follow every step the transaction takes.
Pick a test card to autofill:
Pay by QR codeThe customer scans the code with their phone camera and confirms the payment in their banking app. Funds arrive in seconds.
The customer confirms the payment in the SberBank Online app, without typing in card details.
Simulation only. No data is transmitted or stored.
Your customer pays through our checkout, your own form or a payment link. Card details are tokenized before they leave the browser.
The risk engine scores the transaction in real time and applies your rules, with 3-D Secure only where it is justified.
We pick the acquirer with the best approval odds and cost for that card, and retry elsewhere when a soft decline comes back.
Funds land in your balance with a full audit trail, then move to your bank account on the schedule you choose.
Stop guessing why a payment failed. CentralGatePay shows the full lifecycle of each transaction, from the first authorization attempt to the line on your bank statement.
Group failures by bank, BIN and reason code, and recover the ones you actually can.
Payouts are matched to transactions automatically and exported to 1C or your accounting stack.
Receive disputes, attach evidence and track the outcome without leaving the dashboard.
Predictable REST endpoints, idempotency keys on every write, signed webhooks and SDKs for the languages you already use. Most teams take their first payment on day one.
Full set of test cards, forced declines, disputes and webhook replays.
Node, Python, PHP, Go, Java, Swift and Kotlin, plus ready-made plugins for 1C-Bitrix, Tilda and WordPress.
Breaking changes ship behind a version header, and never on a Friday.
# Create an SBP payment and send a 54-FZ receipt curl https://api.centralgatepay.com/v1/payments \ -H "Authorization: Bearer $CGP_SECRET_KEY" \ -H "Idempotency-Key: cgp_90412" \ -d amount=249000 \ -d currency=rub \ -d "payment_method[type]=sbp" \ -d "receipt[email][email protected]"
import CentralGatePay from "@centralgatepay/node"; const cgp = new CentralGatePay(process.env.CGP_SECRET_KEY); const payment = await cgp.payments.create({ amount: 249000, // in kopecks currency: "rub", capture: true, paymentMethod: { type: "card", token: "tok_2Mr9x4Lp" }, receipt: { email: "[email protected]", vat: "vat22" } }, { idempotencyKey: "cgp_90412" }); console.log(payment.status); // "succeeded"
import os, centralgatepay client = centralgatepay.Client(api_key=os.environ["CGP_SECRET_KEY"]) payment = client.payments.create( amount=249000, # in kopecks currency="rub", capture=True, payment_method={"type": "card", "token": "tok_2Mr9x4Lp"}, receipt={"email": "[email protected]", "vat": "vat22"}, idempotency_key="cgp_90412", ) print(payment.status) # "succeeded"
Card data is encrypted at the field level, vaulted as tokens and isolated from your systems. Our controls are audited every year and monitored every second.
Compliance with the card industry's data security standard, reassessed by an auditor every year.
Card numbers are replaced by tokens the moment they are entered, so raw credentials never reach your stack.
Liability shift where it matters, and a frictionless checkout for low-risk customers.
Anomaly detection on volume, velocity and geography, with alerts routed to your team in real time.
Customer personal data is stored and processed on servers in Russia, as required by 152-FZ.
Multiple data centers and automatic failover between acquirers when one of them is down.
Same balance, same reconciliation file.
Whether you sell once or bill every month, the same infrastructure adapts to how your revenue actually behaves.
High-volume card acquiring with installments, one-click checkout and abandoned-cart recovery.
Subscriptions, usage-based billing, invoices and 54-FZ receipts.
Seller onboarding, split settlement and payouts on your own schedule.
Payment links, recurring plans and reconciliation for teams without engineers.
You pay only on successful transactions, with no setup fee and no monthly fee. Move the sliders and the estimate updates instantly.
Rates are preliminary; exact terms are fixed in your contract.
This is an estimate. Retries assume about 4% of card payments get a soft decline and 33% of those go through on retry. Your exact rate depends on volume and risk profile, and is fixed in your contract.
A bank gives you card acceptance. We give you everything around it, under one contract.
Compared with typical online acquiring terms at a bank. Terms at any specific bank may differ.
Get startedDidn't find your answer? Message us on Telegram and we'll reply within 15 minutes.
Most businesses complete onboarding and take their first payments within one or two business days. Technical integration with our SDKs usually takes a day, and we run the first transactions with you in the sandbox before issuing production keys.
Mir cards, Visa and Mastercard issued by Russian banks, SBP, SberPay, T-Pay, Mir Pay and pay-in-installments. Every method settles into the same balance.
Card volume settles on the next business day (D+1). Other methods follow the schedule of the underlying payment system. Transfers to your bank account can run daily, weekly or on demand.
No. CentralGatePay's cloud cash register issues 54-FZ receipts and sends them to the customer by email or SMS.
If you use our hosted checkout or widget, card data never touches your servers, so your requirements stay minimal. If you collect card data directly, we'll help you map the requirements that apply.
You pay only on successful transactions, with no setup fee and no monthly minimum. Your rate depends on volume, method mix and risk profile, and we put it in writing before you sign.
You're notified the moment the dispute opens, with the reason code and the deadline. Evidence is submitted from the dashboard or via API, and the case is tracked until the final decision.
Send us a request and a manager will get back to you within one business hour with a rate that fits your volume.