Tinkoff Business

Overview

The node integrates with the Tinkoff Business Acquiring API, specifically supporting operations related to recurring payments and card management. For the Remove Card operation under the Recurring resource, it allows users to remove a saved payment card associated with a customer.

This node is beneficial in scenarios where businesses need to manage customers' saved cards for subscription or recurring billing purposes. For example, if a customer wants to delete a stored card from their profile, this node can be used to securely remove that card from the Tinkoff system.

Practical example:

• An e-commerce platform uses this node to allow customers to remove outdated or compromised cards from their saved payment methods.
• A subscription service automates card removal when a user cancels their subscription or updates their payment details.

Properties

Note: Although not listed in the provided properties JSON, the code expects a rebillId (referred to as CardId in the API call) to identify which card to remove. This should be supplied as an additional input property named "Rebill ID" or similar.

Output

The node outputs the response from the Tinkoff API wrapped in the standard n8n execution data format. The output JSON typically contains the result of the Remove Card API call, indicating success or failure 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 authentication.
• The node depends on the Tinkoff Acquiring v2 API endpoints.
• Proper configuration of credentials including terminal key, password, base URL, and optional logging settings is necessary.

Troubleshooting

• Common issues:

  • Missing or invalid Customer Key or Rebill ID will cause the API call to fail.
  • Incorrect API credentials or misconfiguration may lead to authentication errors.
  • Network connectivity problems can prevent successful 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 webhook signature verification fails, an error "Invalid webhook signature / Неверная подпись вебхука" is thrown.
  • Attempting to use unsupported operations under the Reports resource results in a clear error indicating those endpoints are unavailable.

• Resolution tips:

  • Verify that all required input parameters (Customer Key, Rebill ID) are correctly set.
  • Ensure API credentials are valid and have the necessary permissions.
  • Check network access and firewall settings.
  • Review the exact error message for clues and consult Tinkoff API documentation for specific error codes.

Links and References

• Tinkoff Business Acquiring API Documentation
• n8n Documentation on Creating Custom Nodes
• Tinkoff Recurring Payments Overview (in Russian)

If you want me to include details about other operations or resources, please provide the relevant names or properties.