The payment infrastructure for Paysido developers is built on the principles of ease of integration and reliability. REST API, ready-made SDKs, widgets and plugins for popular CMSs allow you to enable payment acceptance on a website or in an application in one or two business days - without complex technical expertise and lengthy approvals.
Paysido is a payment service certified according to the PCI DSS standard. All financial transactions are processed in a secure environment: bank card data is not stored on the merchant’s side, data transfer is carried out using the TLS 1.2+ protocol. The platform architecture ensures high availability (99.9% uptime) and horizontal scaling for any volume of transactions.
The developer can choose the integration method depending on the project architecture and the required flexibility. Paysido supports several approaches - from ready-made plugins to a full-fledged API.
Three main methods are available: REST API for complete control over the payment flow, an embedded widget for a quick start without server logic, and ready-made plugins for CMS. The choice of method is determined by the technical maturity of the project and the time allocated for development.
Paysido provides ready-made modules for WordPress / WooCommerce, Tilda, Bitrix, OpenCart and other popular platforms. Installation is performed through a standard plugin manager: download the module, specify the API key from your business dashboard - integration is complete. Setup takes about 15 minutes.
The embedded payment widget is connected with one line of JavaScript and displays the payment form on top of the site page. The widget is adapted for mobile devices and supports accepting Visa, Mastercard, MIR cards, as well as payment via SBP. The appearance of the widget is customized to match the site design using CSS parameters.
Payment designer is a tool for creating custom payment forms without writing server code. The developer sets the parameters (amount, description, list of products) through a visual interface, receives a ready-made code for inserting into the site or a link for posting in any channel.
Paysido supports all current payment acceptance scenarios on the website and in mobile applications. Each method is accompanied by detailed query examples in the documentation.
To create a payment via the API, send a POST request to the /v1/payments endpoint with the parameters of the amount, currency and description. In the response you will receive payment_id and a link to redirect the client to the payment page. After the transaction is completed, the system sends a webhook to the specified callback URL with the operation status.
Initialize the widget on the page by calling Paysido.Widget.open({ amount, orderId, description }). The widget independently processes the input of card data, 3-D Secure and notification of the result - the server part receives only the final payment status via a webhook.
To accept payments in instant messengers (Telegram, VK), use the API for generating payment links. The /v1/payment-links method creates a short link with pre-filled parameters: the client follows the link and pays in the standard interface. The link lifetime and payment parameters are configured during creation.
To integrate an offline terminal, use the SDK for Android and iOS or the REST API in card-present mode. Payment scenarios with physical card swiping, QR payment via SBP and accepting payments through third-party POS terminals are supported. Terminal initialization and transaction management are performed through a single API interface.
Recurring payments allow funds to be automatically debited on a schedule without the client having to re-enter card details. To activate a recurrent script, specify recurrent: true when creating the first payment - the client enters the card once, after which it is saved in tokenized form.
Starting a recurrent cycle - a POST request to /v1/subscriptions indicating customer_id and payment template. Stopping a subscription: PATCH /v1/subscriptions/{id} with the parameter status: cancelled. All changes are immediately reflected in the merchant’s business dashboard.
Supported intervals: daily, weekly, monthly, custom. When using a custom interval, pass a cron expression to the schedule field. The system automatically creates scheduled payments according to the schedule and sends notifications about the result of each debit.
To change the amount of an active subscription, send a PATCH request to /v1/subscriptions/{id} with the new amount value. The change is applied from the next scheduled payment. The history of amount changes is available in the subscription details via GET /v1/subscriptions/{id}/history.
Secure transaction - escrow service: the buyer's funds are reserved in the Paysido account and transferred to the seller only after confirmation of the fulfillment of obligations. The tool is suitable for marketplaces, C2C platforms and any transactions where the parties do not know each other personally.
To activate the secure transaction mode, contact the Paysido manager: the functionality is connected as an addition to the main agreement. Once activated, the /v1/safe-deals methods become available in the API for creating, confirming and canceling secure transactions.
Two schemes are supported: two-way (buyer → escrow → seller) and three-way (buyer → escrow → platform → seller). In the second scheme, the platform receives a commission automatically upon the final transfer of funds.
For testing, use a sandbox environment with separate API keys. The test circuit completely reproduces the logic of the production environment. A set of test cards with various scenarios (successful payment, rejection, 3-DS, insufficient funds) is available in the developer’s business dashboard.
In sandbox mode, the online cash register operates in the test mode of the Federal Tax Service: checks are generated, but not transmitted to the tax authority. To check the correctness of fiscal data, use the built-in check validator in the “Testing” section of your business dashboard.
Complete technical documentation for all API methods is available in OpenAPI 3.0 format. Each method contains a description of parameters, examples of requests and responses in several programming languages (Python, PHP, Node.js, Java, Go).
The FAQ section contains answers to typical technical questions: setting up webhooks, working with returns, handling API errors, features of working with 3-D Secure and the specifics of fiscalization under various taxation regimes.
Technical support for developers is available by email dev@paysido.com and in Telegram chat. Priority support with a 2 hour SLA is available on Enterprise plans. In standard mode, response time is up to one business day.
The API returns standardized error codes in the error.code field. Class 4xx - client errors (incorrect parameters, insufficient rights, object not found). Class 5xx - server errors, in which it is recommended to repeat the request with an exponential delay. A complete reference book of codes with descriptions and processing recommendations is in the documentation.
Each payment goes through a fixed set of statuses: created → processing → succeeded / failed / canceled. Refunded status is assigned to a full or partial refund. The current status is available via GET /v1/payments/{id} or via a webhook notification.
Webhook notifications are sent to the specified callback URL whenever the transaction status changes. Supported event types: payment.succeeded, payment.failed, payment.cancelled, refund.succeeded, subscription.renewed, subscription.failed. To test webhooks, use the “Resend” function in your business dashboard.
Paysido provides official SDKs for popular languages and frameworks. Each SDK includes out-of-the-box methods for all API operations, automatic error handling and retry requests, and built-in logging for debugging.
The API is built using REST architecture. Base URL: https://api.paysido.com/v1. All requests and responses are sent in JSON format. To ensure idempotency of operations, use the Idempotency-Key header when creating payments and returns.
Authentication is performed via HTTP Basic Auth: the Secret Key from your business dashboard is transferred as a login, the password field remains empty. For server requests, use Secret Key, for client scenarios (widget, mobile application) - Public Key. Key rotation is available in the “Settings” section of your business dashboard.
When passing through the 3-D Secure API, it returns the payment.pending status and a URL to redirect the client to the bank confirmation page. After passing verification, the client returns to the return_url specified when creating the payment. The final payment status is transmitted via a webhook.
Notifications are sent using the POST method to the webhook_url specified in the store settings. The body of the request contains an event object with fields event, object, and created_at. To confirm receipt, the merchant server must return HTTP 200. If there is no response, the system repeats the sending according to the schedule: after 1, 5, 30 minutes and 6 hours.
List of events that you can subscribe to: payment.succeeded, payment.waiting_for_capture, payment.cancelled, refund.succeeded, deal.closed, payout.succeeded. Subscription to specific types of events is configured in your business dashboard in the “Webhooks” section.
Paysido supports native integration with leading Russian payment services. All methods are available through a single API without the need for separate contracts with each system.
To accept payment via SberPay, pass payment_method_type: sber_pay when creating a payment. The client will be redirected to the SberBank Online application for confirmation. Desktop and mobile scenarios are supported.
Integration with MIR Pay works similarly: payment_method_type: mir_pay. The method is available to individuals with MIR cards. When paying from a mobile device, the client is redirected to the banking application via a deep link.
To generate the SBP QR code, use the /v1/payments method with payment_method_type: sbp. The response returns qr_data (a string for the QR code) and qr_image (a base64 image). Payment through SBP does not require 3-D Secure and is processed instantly.
Before starting integration, you can test the operation of the tools interactively without writing code - in a sandbox environment with test data.
An interactive demo of the widget is available at https://demo.paysido.com/widget. You can check the appearance on different devices, test successful and rejected payment scenarios, and customize the color scheme and set of displayed methods.
The payment builder demo allows you to create a test payment form with arbitrary parameters and get ready-made HTML code for insertion. The demo is available at https://demo.paysido.com/constructor and does not require registration.
.webp)