Tinkoff Business

Interact with Tinkoff Business (Acquiring v2)

Actions9

Overview

This node integrates with the Tinkoff Business Acquiring API (version 2) to manage payment transactions. Specifically, for the Cancel Payment operation under the Payment resource, it allows users to cancel an existing payment by providing its Payment ID.

Common scenarios where this node is beneficial include:

  • Automatically cancelling payments that were initiated but need to be voided due to user cancellation or errors.
  • Managing payment workflows where a payment might need to be reversed before capture.
  • Integrating refund or cancellation logic into automated business processes.

Practical example:

  • A merchant receives an order cancellation request and uses this node to cancel the associated payment transaction in Tinkoff's system to avoid capturing funds.

Properties

Name Meaning
Payment ID The unique identifier of the payment to be cancelled. This is required to specify which payment should be cancelled.

Output

The node outputs JSON data representing the response from the Tinkoff API after attempting to cancel the payment. This typically includes details about the cancellation status and any relevant metadata returned by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for Tinkoff Business Acquiring API with terminal key, password, and optionally base URL and timeout settings.
  • The node depends on the TinkoffClient class internally to communicate with the Tinkoff API endpoints.
  • Proper configuration of credentials in n8n is necessary for authentication.

Troubleshooting

  • Common issues:

    • Invalid or missing Payment ID will cause the API call to fail.
    • Incorrect or expired API credentials will result in authentication errors.
    • Network connectivity problems can prevent communication with the Tinkoff API.

  • Error messages:

    • Errors from the Tinkoff API are caught and rethrown with a prefix "Tinkoff error:" followed by the original message.
    • If the API returns additional description information, it is included in the error details.

  • Resolution tips:

    • Verify that the Payment ID is correct and corresponds to an existing payment.
    • Ensure API credentials are valid and have sufficient permissions.
    • Check network access and firewall settings to allow outbound requests to Tinkoff endpoints.

Links and References

Discussion