Actions9
Overview
This node integrates with the Tinkoff Business Acquiring API (version 2) to manage payment transactions. Specifically, for the Refund Payment operation under the Payment resource, it allows users to refund a previously made payment either fully or partially by specifying an amount in kopecks.
Typical use cases include:
- Refunding customers for returned goods or canceled services.
- Automating partial refunds when only part of an order is returned.
- Managing payment reversals directly from n8n workflows without manual intervention.
Example: After a customer cancels an order, you can trigger this node to refund the full payment or a specified partial amount back to the customer’s card.
Properties
| Name | Meaning |
|---|---|
| Payment ID | The unique identifier of the payment transaction to be refunded. |
| Amount (kopecks) | Optional amount to refund in kopecks (1 ruble = 100 kopecks). If omitted or zero, full refund is processed. |
Output
The node outputs JSON data representing the response from the Tinkoff API after attempting the refund. This typically includes details such as refund status, refunded amount, 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 uses internal client logic to communicate with Tinkoff’s API endpoints.
- Proper configuration of credentials in n8n is necessary for authentication.
Troubleshooting
Common issues:
- Invalid or missing Payment ID will cause the refund request to fail.
- Specifying an amount greater than the original payment may result in an error.
- Network or authentication errors if API credentials are incorrect or expired.
Error messages:
- Errors from Tinkoff API are wrapped and presented with a prefix "Tinkoff error:" followed by the message.
- Signature verification errors occur if webhook tokens do not match expected values.
Resolutions:
- Verify that the Payment ID corresponds to an existing payment.
- Ensure the refund amount does not exceed the original payment amount.
- Check and update API credentials if authentication fails.
- Confirm webhook payloads have valid signatures if using webhooks.