Skip to content

Payment systems ​

Settings → Payment systems — subsections Payments, Payment methods, Russian banks.

Payments ​

System cards by group: crypto processing, ruble acquiring, P2P. A card holds keys (stored encrypted; the panel shows only “Configured”), a switch and return URLs after successful and failed payment.

Payment methods ​

Which coins and networks are accepted through which system. If no system is connected, an operator issues the address or bank details manually.

Russian banks ​

Sberbank, T-Bank, Alfa-Bank, VTB, SBP. Daily limits per client card: amount and number of orders per day — protection against splitting and money mules.

Yuan ​

Crypto ⇄ yuan directions via Alipay and WeChat — with their own P2P rate and fee. Connected with the same settings as other directions.

Auto-acceptance and auto payout (Heleket) next version ​

  • Auto-acceptance — if a coin is accepted via Heleket (Payment methods), the invoice is issued automatically within seconds and “Paid” is set from the payment system's response. Postings use the amount actually received; reconciliation and AML screening are filled automatically. KYC threshold, grey rate and manual client review still go through an operator.
  • Auto payout up to a limit — Payment systems → Auto payout. Only the owner can enable it, with a 2FA code; by default 100 $ per order and 500 $ per day. The direction must be in “Auto” or “Auto up to limit” mode; the order card shows why an order did not go out automatically.
  • Emergency stop — the owner and a role with the “Emergency stop auto payouts” permission.
  • No double payouts — a repeated request returns the same payout, one payout per order, an “unknown result” is never retried automatically. A payout error triggers a Telegram alert and the “Payout error” status.
  • Payout key — a separate field in the system card; only the background worker decrypts it, not the website.
  • Logs of incoming notifications and processing requests (without keys), a “Test connection” button.

Documentation of the OneSwaper exchange engine