BILLmanager 6

T-bank

To use the T-bank payment module, you need to register in the payment system and configure the module in BILLmanager.

Supported payment methods
Bank cardCashE-walletMobile paymentInternet banking

Maestro,
Mastercard,
Visa,
«Мир»



Google Pay,
Apple Pay

Supported features

Payment return

Recurring payments

Subscriptions

Configuration on BILLmanager side

The module is installed from the latest available version of the product and requires an update of the BILLmanager platform, because the module version cannot be higher than the platform version.

To create a payment module, enter Provider Payment methods → click Add. The payment module adding wizard consists of the following steps:

  1. Select a payment methods: "T-bank".
  2. Integration settings. Specify the data for integration:
    Activate the Add New Client option to display a link to register with the handler's system.
    Complete the form using the details of an existing client in the handler's system:
    1. Terminal ID — terminal ID for connecting to the Tinkoff API. These details are provided when you register in the payment system;
    2. Terminal password — terminal password for connecting to the Tinkoff API. These details are provided when you register in the payment system;
    3. Use notification address from the terminal's client area — determines where the link will be sent to clients when they make payments:
      • option enabled — from the terminal's client area;
      • option disabled — from BILLmanager.
    4. Recurring payments - the option includes use of recurring payments and creation of saved payment methods. Recurring payments in BILLmanager are used for automatic personal account topup . If you set up auto-payment on the client side, the payment of 1 ruble will be made automatically. This is necessary to confirm that the bank card is active. When the recurring payment activation procedure is completed, this payment will be canceled.
      If the flag is active, specify:

      • Return page after a successful auto-payment - the page to which the payer will be redirected if the auto-payment is successful. Use the BILLmanager page https://domain.com/billmgr?func=payment.recurring.success or a discretionary page;
      • Return page after an unsuccessful auto-payment - the page to which the payer will be redirected if the auto-payment fails. Use the BILLmanager page https://domain.com/billmgr?func=payment.recurring.fail or a discretionary page;
      • Return page after an auto-payment in progress - the page to which the payer will be redirected if the auto-payment is in progress. Use the BILLmanager page https://domain.com/billmgr?func=payment.pending or a discretionary page.

        Comments
        Note.
        The creation of recurring payments is only confirmed by notifications. If BILLmanager has not received a notification from Tinkoff, no new auto-payment or a saved payment method will be created.
        Auto-payments and saved payment methods already created will work even without notifications.
    5. Taxation system - allows you to choose the system of taxation used to be specified when a receipt is generated;
    6. Allow payment refund - if this option is enabled, payment refunds are allowed.
  3. Payment method settings. Configure internal (within BILLmanager) parameters of the service payment module. For more details, see How to add a payment gateway module.

Additional information

Payment refund

To allow payment returns, enter Provider → Payment methods → Edit button → Allow payment refund option. Refunds are supported for payments with the “Credited” status.

Logging

Logs of interaction between the billing platform and Tinkoff are written to the following files:

  • /usr/local/mgr5/var/pmtinkoff.log — log file of payment module settings, recurring payments and refunds, scheduled check of payment statuses;
  • /usr/local/mgr5/var/tinkoffpayment.log — payments log file;
  • /usr/local/mgr5/var/tinkoffnotification.log — notifications log file;
  • /usr/local/mgr5/var/tinkoffrecurring.log — recurring payment settings log file.