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 cards and transactions. Specifically, for the Recurring resource and List Saved Cards operation, it retrieves a list of saved payment cards associated with a given customer key.

Common scenarios where this node is useful include:

  • Retrieving all saved cards for a customer to display them in a user interface.
  • Managing recurring billing by listing stored cards before charging or removing them.
  • Auditing or verifying which cards are currently saved for a customer.

Practical example:

  • An e-commerce platform wants to show a logged-in user all their saved credit/debit cards so they can select one for a new purchase or remove an old card.

Properties

Name Meaning
Customer Key A unique identifier for the customer whose saved cards you want to list.

Output

The output is a JSON object containing the response from the Tinkoff API's GetCardList method. This typically includes details about each saved card such as card ID, masked card number, expiration date, and other metadata related to the saved cards.

The node does not output binary data for this operation.

Example output structure (simplified):

{
  "Success": true,
  "ErrorCode": "0",
  "Message": "OK",
  "CustomerKey": "customer123",
  "Cards": [
    {
      "CardId": "card_abc123",
      "Pan": "**** **** **** 1234",
      "ExpDate": "12/24",
      "CardType": "Visa"
    },
    {
      "CardId": "card_def456",
      "Pan": "**** **** **** 5678",
      "ExpDate": "11/23",
      "CardType": "MasterCard"
    }
  ]
}

Dependencies

  • Requires an API key credential for Tinkoff Business Acquiring API v2.
  • The node uses the Tinkoff client library internally to communicate with the API.
  • Proper configuration of credentials including terminal key, password, base URL, and optional timeout and logging settings is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing customer key will cause the API call to fail.
    • Network or authentication errors if API credentials are incorrect or expired.
    • If the Tinkoff API service is down or unreachable, calls will fail.

  • Error messages:

    • Errors returned from the Tinkoff API are wrapped and presented with the prefix "Tinkoff error:" followed by the message.
    • Signature verification errors occur if webhook tokens do not match expected values.

  • How to resolve:

    • Verify that the customer key is correct and corresponds to an existing customer.
    • Check that API credentials are valid and have required permissions.
    • Ensure network connectivity to the Tinkoff API endpoint.
    • For webhook signature errors, confirm that the webhook secret/password matches the configured value.

Links and References

Discussion