Payment Service Overview

Payment Service AntiDDOS Router is a payment transaction routing service designed for dynamic payment switching between banks. Payment Service AntiDDOS Router simultaneously connects to payment gateways of several banks that the Partner (merchant) works with, and when an order is received, routes the order to one bank or another based on routing rules that are developed individually for the Partner.

The Payment Service API largely replicates the bank payment gateway API (see main differences here). If the Partner is already integrated with one of the acquiring banks, the Payment Service API will be clear and familiar to them.

Payment Methods and Routing

Payment Methods

Payment Service supports bank card payments, as well as Vendor Pays — payment methods of banks and payment systems.

New or saved card (stored credentials)

SBP, including Digital Ruble

Yandex Pay and Yandex Split (via Yandex Paybox)

Mir Pay

SberPay, Alfa Pay, T-Pay

Routing

Partner sets payment routing rules between their banks based on commission optimization for certain transactions.

Routing by all available payment parameters

Payment balancing between banks in specified percentage ratio

Vendor Pays payment to banks where Partner has these Vendor Pays connected

Resilience to failures on bank side

Simple and Advanced Integration

Payment Service Payment Page

Customer makes payment on Payment Service payment page.

Payment Service payment page is not tied to banks

All payment methods that Partner connected in their banks are available

Customization and branding according to Partner design

Minimal API usage

Partner's Own Payment Page

Partner accepts payment in their mobile or web application using Payment Service API.

API for integration without using Payment Service Payment Page

Mobile SDK Core for payment data encryption

Web SDK Payment for secure card data collection on Partner page

Requires software development

Key Benefits

Resilience to failures on bank side

Payment Service ensures resilience to failures and unforeseen situations on acquiring bank side

In case of failures at one acquirer, traffic is automatically switched to another

Exclude bank from routing for a specified interval (for example, during maintenance)

Fix specific payment methods to a particular bank (for example, SberPay — only Sberbank), without redirection

Contact support service for configuration.

Currency conversion during payment

Partner can place orders in one currency and process payments in another.

Payment service converts order currency to target currency of selected bank

Source order currency can be hidden both from target bank and the client

Partner can configure additional commission for conversion

Conversion at Central Bank exchange rate

Saved payment data

Payment service supports saving payment data for subsequent payments.

Payment with saved cards on payment page

Recurring charges

Installment payments

Payment with saved payment data Vendor Pays (SberPay, Yandex Pay, Fast Payment System, T-Pay, etc.)

Fiscal data operators

Payment service allows using fiscalization that is connected in Partner's banks.

Fiscalization is configured on bank side

Receipt data request via Payment service API

Partner Connection

To connect to the Payment Service, the Partner must:

Enter into an agreement with each acquiring bank.
Contact the support service to register in the payment gateways of each bank (if the Partner is not yet registered there), as well as to register in the Payment Service.

As a result of registration, the Partner receives the API address of the Payment Service, as well as a login and password for sending API requests.

Payment Service Limitations

Vendor Pays bonuses write-off is not supported.
For all banks, the same credentials (login and password) and settings must be used for a single merchant.

Payment Routing

The payment service AntiDDOS Router routes the order payment when the "Pay" button is clicked on the payment page or when a payment method is called (e.g., paymentOrder.do, paymentOrderBinding.do, /alfapay/paymentOrder.do, etc.). Routing is performed according to the rules set in the Payment Service. To configure routing rules, please contact support. To check current routing rules and other settings, make a request to /settings/getRouterParams.do.

Depending on the payment method, the following routing options are available:

Payment Method	Routing Options
Card	By any available payment parameters: order amount and parameters (features, jsonParams), card issuing bank, payment system, card product type (debit or credit), specific range, etc. Percentage-based distribution between specified banks Strictly to the bank specified by the Partner in the `gwId` parameter of register.do or registerPreAuth.do request. If this bank is unavailable, no alternative is selected and the payment fails. To a failover bank if the selected bank is unavailable. If no failover banks are specified, the Payment Service may automatically select an alternative bank when possible.
Card Binding	Generally same as for cards, but may depend on binding type and settings, see Routing
SBP (Fast Payments System)	Payments can only be routed to those banks that Partner agreed with on accepting SBP payments. Additional routing options: By certain payment parameters (amount, `features`, `jsonParams`, etc.) Percentage-based distribution between specified banks To a failover bank (one of the Partner's SBP banks) if the selected bank is unavailable. When paying from a mobile device, routing via the Client's bank is available.
SBP Subscriptions	Depends on the way of payment, see Paying with SBP Subscription
Vendor Pays	Payments can only be routed to those banks that Partner agreed with on accepting the corresponding Vendor Pay. Hence, routing one Vendor Pay to multiple banks is only possible if such payment method is supported by multiple banks (for example, Mir Pay).
Vendor Pays stored credentials	Only to the bank where the credentials are stored