Actions10
Overview
The node integrates with the Cryptomus API to facilitate cryptocurrency payment processing. Specifically, the "Create Payment" operation allows users to create a new payment invoice with specified parameters such as amount, currency, and order ID. This is useful for merchants or services that want to accept cryptocurrency payments or fiat payments converted into cryptocurrencies.
Common scenarios include:
- Creating payment requests for customers in various currencies.
- Specifying additional options like callback URLs for payment status updates.
- Handling test payments to verify integration without real transactions.
Example: A merchant can create a payment request of $10.50 USD for order "order-123", optionally specifying a callback URL to receive payment status notifications.
Properties
| Name | Meaning |
|---|---|
| Amount | The payment amount to be charged (e.g., "10.50"). |
| Currency | The fiat currency code for the payment (e.g., "USD", "EUR", "RUB"). |
| Order ID | Unique identifier for the order in your system (e.g., "order-123"). |
| Additional Parameters | Optional collection of extra fields to customize the payment: |
| - Callback URL | URL to receive notifications about payment status changes. |
| - Comment | Comment or note associated with the payment. |
| - Currency for Conversion | Cryptocurrency code to convert the payment into (if applicable). |
| - Error URL | URL to redirect the user if an error occurs during payment. |
| - Exclude Currencies | Comma-separated list of currencies to exclude from payment options. |
| - Lifetime | Invoice lifetime in seconds (default 3600). |
| - Network | Specific blockchain network for the payment. |
| - Payment Method | Cryptocurrency code used for payment (e.g., BTC, ETH). |
| - Return URL | URL to redirect the user after payment completion. |
| - Show Network | Boolean flag to show the network in the payment form. |
| - Success URL | URL to redirect after successful payment. |
| - Wallet Address | Wallet address to which the payment should be sent. |
| - Wallet Address Signature | Signature verifying the wallet address authenticity. |
| Test Payment | Boolean indicating whether this is a test payment (no real transaction). |
Output
The output JSON contains the response from the Cryptomus API after creating the payment. This typically includes details such as:
- Payment ID or UUID assigned by Cryptomus.
- Payment status and URLs for payment processing.
- Invoice details including amount, currency, and order ID.
- Any additional metadata returned by the API.
No binary data is output by this node.
Dependencies
- Requires an API key credential configured in n8n for authenticating with the Cryptomus API.
- The credential must be of the correct API type supporting payment operations.
- The node uses HTTP POST requests to Cryptomus API endpoints.
Troubleshooting
- Invalid Credentials: If the provided API credentials are not of the required type for payments, the node will throw an error indicating the mismatch.
- API Errors: Errors returned by the Cryptomus API (e.g., invalid parameters, network issues) will be surfaced. Users should verify all required fields and network connectivity.
- Missing Required Fields: Ensure that "Amount", "Currency", and "Order ID" are provided; otherwise, the API call may fail.
- Timeouts or Network Issues: Check internet connection and Cryptomus service status if requests time out.
- Continue on Fail: If enabled, errors will be returned as part of the output JSON instead of stopping execution.
Links and References
- Cryptomus API Documentation (for detailed API usage and parameters)
- n8n Documentation on Creating Custom Nodes