Actions9
Overview
This node integrates with the Tinkoff Business Acquiring API (version 2) to manage payment transactions programmatically. Specifically, the Initialize Payment operation creates a new payment session for a specified order amount and customer details. This is useful in e-commerce or service platforms where you want to initiate payments through Tinkoff’s acquiring system, enabling customers to pay online.
Typical use cases include:
- Starting a payment process when a customer places an order.
- Supporting two-stage payments by optionally holding funds before final confirmation.
- Collecting customer contact information (email and phone) for receipts or notifications.
Example: When a user submits an order on your website, this node can initialize the payment session with the exact amount in kopecks, associate it with the order ID, and optionally hold the funds until you confirm the payment later.
Properties
| Name | Meaning |
|---|---|
| Amount (kopecks) | The payment amount in kopecks (integer). For example, 10000 means 100 rubles. |
| Order ID | Unique identifier of the order associated with this payment. |
| Customer Email | Optional email address of the customer. |
| Customer Phone | Optional phone number of the customer in the format +7XXXXXXXXXX (Russian phone format). |
| Hold Funds (Two-Stage) | Boolean flag to enable holding funds instead of immediate capture (two-stage payment flow). |
Output
The node outputs the response from the Tinkoff Acquiring API wrapped as JSON data. This typically includes:
- Payment session details such as payment ID, status, and URLs for payment processing.
- Confirmation whether the initialization was successful.
- Any error messages or codes if the initialization failed.
The output is structured as an array of execution data objects containing the raw API response under the json field.
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for Tinkoff Business Acquiring API with terminal key, password, and optional base URL.
- The node uses the official Tinkoff Acquiring v2 API endpoints.
- Proper configuration of credentials in n8n is necessary for authentication.
- The node depends on internal utility functions for formatting amounts and sanitizing Russian phone numbers.
Troubleshooting
- Invalid credentials or authentication errors: Ensure that the API key credential is correctly configured with valid terminal key and password.
- Incorrect phone number format: The customer phone must be in the Russian E.164 format (+7XXXXXXXXXX). Invalid formats may cause API errors.
- Amount not properly set: The amount must be a positive integer representing kopecks. Zero or negative values will likely cause failures.
- API endpoint unavailability: If the Tinkoff API is down or unreachable, the node will throw an error indicating connection issues.
- Error messages from Tinkoff: The node surfaces Tinkoff-specific error messages. Review the message and description fields for troubleshooting.
- Hold funds option misuse: Enabling hold without understanding two-stage payment flows may lead to unexpected payment states.