Actions9
Overview
The node integrates with the Tinkoff Business Acquiring API (version 2) to manage payment transactions. Specifically, the "Confirm Payment" operation allows users to confirm a previously initialized payment, optionally specifying an amount for partial confirmation. This is useful in scenarios where payments are authorized but require explicit confirmation before funds are captured, such as two-stage payment flows or partial captures.
Practical examples:
- Confirming a full payment after order fulfillment.
- Partially confirming a payment if only part of an order is shipped.
- Automating payment confirmation workflows within e-commerce or billing systems.
Properties
| Name | Meaning |
|---|---|
| Payment ID | The unique identifier of the payment to confirm. |
| Amount (kopecks) | Optional amount in kopecks to partially confirm the payment. If omitted or zero, confirms full amount. |
Output
The node outputs JSON data representing the response from the Tinkoff API's payment confirmation call. This typically includes details about the confirmed payment status, amounts, and any relevant metadata returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Tinkoff Business Acquiring API.
- The node depends on the external Tinkoff Acquiring API service endpoint.
- Proper configuration of credentials including terminal key, password, and base URL is necessary.
- The node uses internal utility functions to ensure amounts are correctly formatted in kopecks and phone numbers sanitized.
Troubleshooting
- Common issues:
- Invalid or missing Payment ID will cause the API call to fail.
- Specifying an amount greater than the original payment amount may result in errors.
- Network or authentication failures due to incorrect API credentials.
- Error messages:
- Errors from the 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 initialized payment.
- Ensure the amount specified does not exceed the authorized amount.
- Check API credentials and network connectivity.
- For webhook-related errors, confirm the webhook secret/password matches the configured value.