Actions5
- Bank Slip Actions
- Truemoney Wallet Actions
Bank Slip → Verify by Payload
AI-generatedOverview
This node verifies bank slips by using the QR code payload data from the slip. It sends the payload to the EasySlip API to validate the slip details. The node supports filtering results by receiver bank code and receiver name, allowing users to route matched and unmatched slips to different outputs. It also supports checking for duplicate slips and enabling debug logging for troubleshooting.
Use Case Examples
- A user wants to verify multiple bank slips by scanning their QR code payloads and filter the results to only include slips from a specific bank.
- A business automates the verification of bank slips received via email by sending the QR code payloads to this node and routing unmatched slips for manual review.
Properties
| Name | Meaning |
|---|---|
| Payload | QR code data from the bank slip, required for verification. |
| Check Duplicate | Whether to check for duplicate slips during verification. |
| Additional Options | Optional filters and settings such as filtering by receiver bank code, receiver name, and enabling debug logging. |
Output
JSON
json- The JSON response from the EasySlip API containing verification details of the bank slip.
Dependencies
- EasySlip API with an access token credential
Troubleshooting
- If the node throws an error about missing binary data, ensure the correct input property is specified and contains data.
- A 400 error with message 'duplicate_slip' indicates the slip has been detected as a duplicate; the node routes these slips according to filter settings.
- Enable debug logging to see detailed request and response information for troubleshooting.
Links
- EasySlip API Documentation - Official API documentation for EasySlip, used for verifying bank slips.