Actions10
Overview
This node integrates with the Cryptomus API to facilitate cryptocurrency payment processing and related operations. It supports creating payments, retrieving payment details and history, refunding payments, checking balances, listing supported currencies, and testing or resending webhooks.
Common scenarios include:
- Creating a new cryptocurrency payment invoice for customers.
- Querying payment status or history for reconciliation.
- Refunding payments or blocked funds back to users.
- Monitoring account balance of cryptocurrencies.
- Testing webhook integrations to ensure notifications work correctly.
For example, an e-commerce platform can use this node to generate crypto payment requests, track their statuses, and handle refunds automatically.
Properties
| Name | Meaning |
|---|---|
| Test Payment | Whether this payment is for testing purposes (boolean: true or false) |
Note: The node has many other properties depending on the selected operation, but since only "Default" resource and operation were requested, and only "Test Payment" property was provided, only that is listed here.
Output
The node outputs JSON data representing the response from the Cryptomus API for the selected operation. The structure varies by operation but generally includes:
- For payment creation: details of the created payment including amount, currency, order ID, payment URL, and status.
- For payment queries: detailed payment information such as status, amounts, timestamps.
- For refunds: confirmation of refund request status.
- For balance: current cryptocurrency balances.
- For currency list: available cryptocurrencies and payment methods.
- For webhook tests: result of sending test webhook.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential configured in n8n with access to the Cryptomus Payment API.
- Uses HTTP requests to communicate with Cryptomus endpoints.
- No additional external dependencies beyond the Cryptomus API and n8n's HTTP helper.
Troubleshooting
- Invalid Credentials Error: If credentials do not have the required API type for payments, the node throws an error indicating the mismatch. Ensure the API key used is authorized for payment operations.
- API Request Failures: Network issues or invalid parameters may cause API errors. The node attempts to provide error messages returned by the API.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.
- Common Errors:
- Missing required parameters like amount or currency when creating payments.
- Invalid payment IDs when querying or refunding.
- Incorrect webhook URLs or statuses during webhook tests.
Resolving these typically involves verifying input parameters and ensuring correct API credentials.