Tinkoff Payment

Init payment via Tinkoff API

Overview

This node integrates with the Tinkoff payment API to initialize a payment transaction. It is designed to facilitate online payment processing by sending payment details such as amount, terminal key, and payment type to Tinkoff's secure payment endpoint. This node is useful in scenarios where you want to automate payment initiation within workflows, for example, when processing orders or subscriptions on websites or applications that use Tinkoff as a payment gateway.

Practical examples include:

  • Automatically initiating a payment when a new order is created.
  • Processing recurring payments by setting the recurrent flag.
  • Integrating payment initialization into custom checkout flows.

Properties

Name Meaning
Password The password used to generate a security token for authenticating the payment request.
Amount The payment amount to be charged (in the smallest currency unit, e.g., kopecks).
Terminal Key The terminal identifier provided by Tinkoff to identify the merchant account.
Pay Type The type of payment method to be used (e.g., card, mobile payment, etc.).

Output

The node outputs JSON data containing the response from the Tinkoff API after attempting to initialize the payment. The output includes fields returned by the API such as status, payment URL, payment ID, and any error messages if applicable.

No binary data is output by this node.

Dependencies

  • Requires an active internet connection to communicate with the Tinkoff payment API endpoint at https://securepay.tinkoff.ru/v2/Init.
  • Needs valid credentials: a password and terminal key provided by Tinkoff.
  • Uses the axios library for HTTP requests.
  • Uses the crypto module to generate a SHA256 hash token for request authentication.
  • Uses the uuid library to generate unique identifiers for OrderId and CustomerKey.

Troubleshooting

  • Common issues:

    • Invalid or missing credentials (password or terminal key) will cause authentication failures.
    • Incorrect amount format or zero amount may result in API errors.
    • Network connectivity problems can prevent successful API calls.
    • Unsupported or incorrect pay type values might lead to payment initialization failure.

  • Error messages:

    • Errors thrown by the node typically originate from the Tinkoff API response or network issues.
    • The node throws a generic API error with details if the HTTP request fails.

  • Resolution tips:

    • Verify that the password and terminal key are correct and active.
    • Ensure the amount is a positive number representing the smallest currency unit.
    • Confirm that the pay type matches one of the accepted values by Tinkoff.
    • Check network connectivity and firewall settings.
    • Review the Tinkoff API documentation for specific error codes and their meanings.

Links and References

Discussion