Tinkoff Business

Interact with Tinkoff Business (Acquiring v2)

Actions9

Overview

This node integrates with the Tinkoff Business Acquiring API (version 2) to manage payment operations. Specifically, for the Payment - Get Payment Status operation, it retrieves the current status of a specified payment by its Payment ID.

Common scenarios where this node is beneficial include:

  • Checking whether a payment has been successfully processed, is pending, or failed.
  • Monitoring payment states in automated workflows to trigger subsequent actions based on payment completion.
  • Reconciling payments in accounting or CRM systems by verifying payment statuses programmatically.

Practical example:

  • After initiating a payment through the Tinkoff system, you can use this node to periodically check the payment status and update your order management system accordingly.

Properties

Name Meaning
Payment ID The unique identifier of the payment whose status you want to retrieve. This is required.

Output

The node outputs JSON data representing the payment status response from the Tinkoff API. The structure typically includes details such as:

  • Payment state/status (e.g., authorized, confirmed, canceled).
  • Payment identifiers and metadata.
  • Any additional information returned by the API about the payment.

If the node supports binary data output, it is not applicable here since this operation deals solely with JSON payment status data.

Dependencies

  • Requires an API key credential for authenticating with the Tinkoff Business Acquiring API.
  • The node uses the Tinkoff API client internally to make requests.
  • Proper configuration of the API credentials including terminal key, password, base URL, and optional logging settings is necessary.

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 may prevent successful API calls.

  • Error messages:

    • Errors from the Tinkoff API are wrapped and presented with a prefix "Tinkoff error:" followed by the specific message.
    • If the API returns detailed error descriptions, these are included in the error details.
    • For webhook usage, an "Invalid webhook signature" error indicates a mismatch in security tokens, suggesting misconfiguration or tampering.

  • Resolutions:

    • Ensure the Payment ID is correct and corresponds to an existing payment.
    • Verify that API credentials are valid and have the necessary permissions.
    • Check network access and firewall settings.
    • For webhook errors, confirm that the webhook secret/password matches between Tinkoff and n8n.

Links and References

Discussion