Cryptomus Payment icon

Cryptomus Payment

Working with the Cryptomus API for processing cryptocurrency payments

Actions10

Overview

This node integrates with the Cryptomus API to manage cryptocurrency payments and related operations. It supports creating new payments, retrieving payment lists or histories, fetching payment details, refunding payments, resending webhooks, testing webhook functionality, checking balances, and listing available cryptocurrencies.

The Get List of Payments operation specifically retrieves a paginated list of payments filtered by various parameters such as date range, status, order ID, and page size. This is useful for financial reporting, reconciliation, or monitoring payment statuses in bulk.

Practical examples:

  • Fetch all confirmed payments within a specific date range to generate a sales report.
  • Retrieve pending payments to follow up on incomplete transactions.
  • Paginate through large sets of payment data for auditing purposes.

Properties

Name Meaning
Date From Filter payments starting from this date (format: YYYY-MM-DD).
Date To Filter payments up to this date (format: YYYY-MM-DD).
Filter by Status Filter payments by their status. Options: Confirmed, Error, Expired, Payment Received, Pending Payment.
Items per Page Number of payment records to return per page (pagination size).
Order ID Filter payments by a specific order identifier.
Page Number The page number of results to retrieve (for pagination).
Test Payment Boolean flag indicating whether to include test payments.

Output

The output is an array of JSON objects representing the response from the Cryptomus API for the requested payment list. Each object contains payment details according to the API's response schema, which typically includes fields like payment ID, amount, currency, status, timestamps, and related metadata.

No binary data output is produced by 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 external dependencies beyond the Cryptomus API and n8n's HTTP request helper.

Troubleshooting

  • Invalid Credentials Error: If the provided API credentials are not of the required "Payment" type, the node will throw an error indicating the mismatch. Ensure that the correct API key with payment permissions is used.
  • API Request Failures: Network issues or invalid parameter values may cause API errors. Check the error message returned by the API for guidance.
  • Pagination Issues: If too many items are requested per page or an invalid page number is specified, the API might return empty or partial results. Adjust the Items per Page and Page Number accordingly.
  • Date Format Errors: Dates must be in YYYY-MM-DD format; otherwise, the API may reject the request.

Links and References

Discussion