Overview
This node is a webhook trigger designed to process incoming webhook events from the Cryptomus payment platform. It listens for various payment-related events such as payment creation, confirmation, completion, errors, expiration, and pending confirmations. The node verifies the authenticity of each webhook request by validating a signature header against the payload and configured API credentials.
Common scenarios where this node is beneficial include:
- Automating workflows based on payment status changes (e.g., sending notifications when a payment is completed).
- Updating internal systems or databases when new payments are created or their statuses change.
- Handling payment errors or expirations to trigger compensating actions.
For example, you could use this node to trigger an order fulfillment workflow once a payment is confirmed or to alert your support team if a payment error occurs.
Properties
| Name | Meaning |
|---|---|
| Event Types | Select one or more payment event types to listen for. Options: - Payment Completed - Payment Confirmed - Payment Created - Payment Error - Payment Expired - Payment Pending Confirmation |
Output
The node outputs data in the json field containing the full webhook payload received from Cryptomus. This includes all details about the payment event, such as merchant ID, payment status, and other relevant information sent by Cryptomus.
If the webhook event's status matches one of the selected "Event Types," the node outputs an array with one item containing the JSON data and HTTP headers of the request. If the event does not match or fails validation, it outputs an empty array, effectively not triggering downstream nodes.
The node does not output any binary data.
Dependencies
- Requires an API key credential for Cryptomus, including a merchant ID and API key, to validate incoming webhook signatures.
- Uses the MD5 hashing algorithm to verify the webhook signature.
- Must be configured with the correct webhook URL in the Cryptomus dashboard to receive events.
Troubleshooting
- Missing sign header: The webhook request lacks the required signature header. Ensure that Cryptomus is correctly configured to send the signature header.
- Missing merchant_id in request body: The webhook payload does not contain the merchant ID. Verify that the webhook payload format has not changed.
- Merchant ID does not match credentials: The merchant ID in the webhook does not match the configured credentials. Check that the correct merchant ID is used in the node credentials.
- Invalid signature: The signature verification failed, indicating possible tampering or incorrect API key configuration. Confirm that the API key is correct and that the webhook payload is unaltered.
- No matching event type: If the webhook event status is not among the selected event types, the node will not trigger downstream workflows. Adjust the "Event Types" property accordingly.
Links and References
- Cryptomus API Documentation (for webhook setup and payload details)
- MD5 Hashing Algorithm (used for signature verification)