Cryptomus Payment

Overview

This node integrates with the Cryptomus API to manage cryptocurrency payments and related operations. It supports a variety of payment-related tasks such as creating payments, retrieving balances, listing available cryptocurrencies, fetching payment details and history, refunding payments, resending webhooks, and testing webhook functionality.

The Get List of Currencies operation specifically retrieves a list of cryptocurrencies supported by the Cryptomus payment system. This is useful for workflows that need to dynamically display or validate available currencies before processing payments.

Practical examples:

• Automatically fetch and display supported cryptocurrencies in a user interface before initiating a payment.
• Validate currency input against the current list of supported currencies.
• Use the currency list to configure payment options dynamically in an automated workflow.

Properties

Note: The provided property isTest is a boolean flag indicating if the payment should be treated as a test payment. Although it is defined globally, it does not affect the "Get List of Currencies" operation directly based on the source code.

Output

The output of the Get List of Currencies operation is a JSON object containing the response from the Cryptomus API endpoint /v1/payment/services. This typically includes details about all available cryptocurrencies supported by the service.

The structure generally looks like:

{
  "currencies": [
    {
      "code": "BTC",
      "name": "Bitcoin",
      "network": "Bitcoin Network",
      ...
    },
    {
      "code": "ETH",
      "name": "Ethereum",
      "network": "Ethereum Network",
      ...
    }
    // more currencies
  ]
}

No binary data output is involved in this operation.

Dependencies

• Requires an API key credential configured with access to the Cryptomus Payment API.
• The node uses HTTP POST requests to communicate with Cryptomus endpoints.
• No additional environment variables are explicitly required beyond the API credentials.

Troubleshooting

• Invalid Credentials Error: If the API key is not of the correct type (must be for "Payment" API), the node throws an error indicating the wrong API type. Ensure you use credentials intended for payment operations.
• API Request Failures: Network issues or invalid parameters may cause HTTP request errors. The node attempts to handle these gracefully but will throw errors unless "Continue On Fail" is enabled.
• Empty or Unexpected Response: If the API returns no currencies or an unexpected format, verify your account permissions and API status with Cryptomus.
• Operation Mismatch: Selecting an unsupported operation or missing required parameters will cause errors. Always ensure the operation is set to "Get List of Currencies" for this use case.

Links and References

• Cryptomus API Documentation — Official API docs for detailed endpoint descriptions.
• n8n Documentation — For general guidance on using n8n nodes and handling credentials.