Features

With this API, you can make payments securely and with ease.

Payment session

All API operations are carried out within a payment session: session. One payment session can include several operations: for example, you can accept and then refund a payment.

You can send payments using one of the two options:

• Initiate the payment when you start a session (as a single request session/init/payment).
• Start a session and then perform a payment (as two requests, session/create and session/start/payment) e.g. to call the payment form the widget or just to obtain the session identifier and use it to monitor what is happening with the payment.

Which cards you can accept for payment

Visa, Mastercard, and Mir.

What operations you can perform

• one-time payments by card, including AFT payments
• delayed capture payments (the amount is held for up to 5 days, and is then debited either in full or partially)
• recurring payments
• refunds (full or partial)
• split payments (the payment is split in two: for example, some of the money goes to the store which sold the goods, and the rest goes to the delivery driver)
• payments via SberPay
• payments via FPS with QR code

How to obtain card details securely

You can pass card details with open parameters or use the payment form widget. In both cases, you must comply with the PCI DSS requirements.

Card identifier

To enable this functionality, please contact your manager at Bank 131.

If you do not store bank card details on your side and you need to understand which card the user is using and whether users' cards overlap, you can use the card identifier feature.

If you have multiple projects (X-PARTNER-PROJECT), a card identifier may be the same or different for each project. Please inform your manager at Bank 131 which option you prefer.

A card identifier is unique and is generated based on the card number and its expiration date. Its value is passed in the new parameter card_id. This parameter can be passed during payments, recurring payments, and refunds.

A card identifier can not be used for making payments or for getting all linked cards.

A card identifier is not a replacement for a token — you will receive both.

Card tokenization

Bank 131 can store tokenized data for Russian cards on the Bank's side. This may be convenient in case you decided not to store the bank card details that demand compliance with the additional PCI DSS requirements, or if you decide not to use the tokenization widget for some reason. You can pass tokenized data to Bank 131 after the first payout transaction and use it for further payouts. Learn more

Tariffs and limits

The tariffs for acquiring are given in your agreement with the Bank. You can discuss them with your manager.

Restricted business

The following categories of businesses and business practices are restricted from using the Bank 131 services.

View restricted business categories