Actions9
Overview
This node integrates with the Tinkoff Business Acquiring API (version 2) to handle various payment-related operations, including recurring payments. Specifically, for the Recurring - Autopayment (Charge) operation, it enables charging a customer automatically using previously saved card details via a rebill ID.
Common scenarios where this node is beneficial include:
- Automating subscription or membership fee collections.
- Charging customers on a recurring basis without requiring them to re-enter payment details.
- Managing saved cards and performing one-click charges securely.
For example, after saving a customer's card once, you can use the "Autopayment (Charge)" operation to charge that customer later by providing their customer key and the rebill ID obtained from the initial payment.
Properties
| Name | Meaning |
|---|---|
| Customer Key | Unique identifier for the customer in the system. |
| Rebill ID | The rebill ID received earlier after the first payment; used to identify the saved card. |
| Amount (kopecks) | The amount to charge in kopecks (1/100 of a ruble). |
Output
The node outputs JSON data representing the response from the Tinkoff Acquiring API for the requested operation. This typically includes details such as transaction status, payment IDs, error messages if any, and other relevant metadata returned by the API.
No binary data output is produced by this node.
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 uses the Tinkoff Acquiring v2 API endpoints.
- Proper configuration of credentials in n8n is necessary to authenticate API calls.
Troubleshooting
Common Issues:
- Invalid or missing customer key or rebill ID will cause API errors.
- Incorrect amount format (not in kopecks) may lead to unexpected results.
- Network or authentication failures due to incorrect API credentials.
Error Messages:
- Errors from Tinkoff API are wrapped and presented with the prefix "Tinkoff error:" followed by the message.
- If the webhook signature verification fails, an error "Invalid webhook signature / Неверная подпись вебхука" is thrown.
- Attempting to use unsupported operations under the "Reports" resource will throw an error indicating these endpoints are not available in this API version.
Resolution Tips:
- Verify that the customer key and rebill ID are correct and correspond to existing saved cards.
- Ensure amounts are provided in kopecks (integer values).
- Check API credentials and permissions.
- For webhook issues, confirm the webhook payload and secret/password match.