Tinkoff Business

Interact with Tinkoff Business (Acquiring v2)

Actions9

Overview

This node integrates with the Tinkoff Business Acquiring API (version 2) to manage recurring payment operations related to customer cards. Specifically, for the Recurring resource and Save Card (Add Customer) operation, it allows you to save a customer's card by adding the customer to the system and initializing a small binding payment to securely store their card details for future charges.

Common scenarios where this node is beneficial include:

  • Setting up recurring billing for subscription services.
  • Saving customer card details securely for later automatic payments.
  • Managing customers' saved cards in your payment system.

Practical example:

  • When a new user subscribes to a service, use this node to save their card information by creating a customer profile and performing a small authorization transaction. Later, you can charge the saved card automatically without requiring the user to re-enter payment details.

Properties

Name Meaning
Customer Key A unique identifier for the customer whose card will be saved or managed.

Output

The node outputs JSON data representing the response from the Tinkoff API calls. For the Save Card (Add Customer) operation, the output includes details about the customer addition and the initialization of the binding payment, such as transaction status, order ID, and any relevant identifiers 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, base URL, and optional settings like timeout and logging.
  • The node depends on the external Tinkoff Acquiring v2 API endpoints for managing recurring payments.
  • Proper configuration of credentials in n8n is necessary to authenticate API requests.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect or missing Customer Key parameter will prevent saving the card.
    • Network or API endpoint errors may occur if the base URL or connectivity is misconfigured.

  • Error messages:

    • Errors from the Tinkoff API are wrapped and presented with the prefix "Tinkoff error:" followed by the specific message.
    • If the operation is unsupported (e.g., reports resource), a clear error is thrown indicating unavailability.
    • Webhook signature validation errors indicate invalid or tampered webhook payloads.

  • Resolutions:

    • Verify that the API credentials are correctly set up and active.
    • Ensure the Customer Key is unique and properly formatted.
    • Check network connectivity and API endpoint URLs.
    • For webhook errors, confirm that the webhook secret/password matches the one configured in Tinkoff.

Links and References

Discussion