Mindz icon

Mindz

Interact with Mindz API

Actions115

Overview

The MindzPay Payment node's List operation retrieves a list of payment records associated with a specified MindzPay account. This node is useful for scenarios where you want to fetch and analyze payment transactions, such as generating reports, monitoring payment statuses, or integrating payment data into other workflows.

For example, you might use this node to:

  • Retrieve the latest 50 payments made to a specific MindzPay account.
  • Filter payments by search terms to find specific transactions.
  • Sort payments by date or amount to prioritize recent or high-value transactions.

Properties

Name Meaning
Account ID The unique identifier of the MindzPay account whose payments you want to list.
Limit Maximum number of payment results to return (minimum 1).
Offset Number of payment results to skip before starting to collect the output list.
Sort By Field to sort the payment results by. Options: ID, Date, Price Total, Status.
Sort Direction Direction to sort the results. Options: Ascending, Descending.
Search A search term to filter the payment results based on matching criteria.

Output

The node outputs an array of payment objects in the json field. Each object represents a payment record with details such as payment ID, date, total price, status, and other relevant payment information.

If the node supports binary data output (not explicitly shown here), it would typically represent attachments or documents related to payments, but this is not indicated in the provided code or properties.

Dependencies

  • Requires an API authentication token credential to connect securely to the Mindz API.
  • Depends on the MindzPay service being accessible and the provided Account ID being valid.
  • No additional external dependencies are indicated.

Troubleshooting

  • Invalid Account ID: If the Account ID is incorrect or does not exist, the node may return an empty list or an error. Verify the Account ID is correct.
  • API Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key or OAuth2 token is properly configured.
  • Limit and Offset Misconfiguration: Setting a limit less than 1 or a negative offset may cause errors or unexpected behavior. Use valid numeric values.
  • Sorting Issues: Sorting by unsupported fields or invalid directions could result in errors or default sorting behavior.
  • Search Term Filtering: Using complex or unsupported search terms might yield no results; verify the search syntax if applicable.

Links and References

Discussion