Cryptomus Payment

Overview

This node integrates with the Cryptomus API to manage cryptocurrency payments and related operations. It supports various actions such as creating payments, retrieving balances, listing currencies, fetching payment details, refunding payments, and testing webhooks.

The Get Balance operation specifically retrieves the current balance information from the Cryptomus account associated with the provided API credentials. This is useful for monitoring available funds before initiating transactions or reconciling accounts.

Practical examples:

• A business can use this node to check their cryptocurrency wallet balance before processing new customer payments.
• Financial teams can automate daily balance checks to update internal dashboards or trigger alerts if funds are low.

Properties

Note: For the Get Balance operation, no additional input properties beyond credentials and the "Test Payment" flag are required.

Output

The output of the Get Balance operation is a JSON object containing the balance information returned by the Cryptomus API. The exact structure depends on the API response but typically includes details such as:

• Available balance amounts in different currencies
• Possibly locked or pending amounts
• Other metadata related to the account balance

No binary data is output by this operation.

Example output (simplified):

{
  "balance": {
    "USD": "1000.00",
    "BTC": "0.05"
  },
  "locked": {
    "USD": "100.00"
  }
}

Dependencies

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

Troubleshooting

• Error: Credentials API type mismatch
  If the credentials used do not have the correct API type (must be for Payments), the node will throw an error indicating the wrong API type. Ensure you configure credentials with the appropriate API access.

• API request failures
  Network issues, invalid credentials, or incorrect parameters may cause HTTP request errors. Check the error message returned by the API for details and verify your credentials and input parameters.

• Empty or unexpected response
  If the balance response is empty or missing expected fields, confirm that the API key has sufficient permissions and that the Cryptomus service is operational.

Links and References

• Cryptomus API Documentation (official API docs)
• n8n documentation on creating custom nodes