Actions7
- Payment Intent Actions
- Portal Actions
- Transaction Actions
Transaction → List Transactions
AI-generatedOverview
This node operation lists transactions from the Bayarcash API with optional filtering capabilities. It is useful for retrieving transaction data based on specific criteria such as order number, status, payment channel, exchange reference number, or payer email. This can help users monitor and analyze payment transactions efficiently.
Use Case Examples
- List all transactions with status 'Success' to generate a report of completed payments.
- Filter transactions by a specific order number to track payment details for that order.
- Retrieve transactions made through specific payment channels like FPX or DuitNow QR for channel-specific analysis.
Properties
| Name | Meaning |
|---|---|
| Order Number | Filter transactions by order number. |
| Status | Filter transactions by status, such as New, Pending, Failed, Success, or Cancelled. |
| Payment Channel | Filter transactions by one or more payment channels. Leave empty to show all channels. |
| Exchange Reference Number | Filter transactions by exchange reference number. |
| Payer Email | Filter transactions by payer email. |
Output
JSON
transactionId- Unique identifier of the transaction.orderNumber- Order number associated with the transaction.status- Status of the transaction.paymentChannel- Payment channel used for the transaction.exchangeReferenceNumber- Exchange reference number related to the transaction.payerEmail- Email of the payer.amount- Amount involved in the transaction.transactionDate- Date and time when the transaction occurred.
Dependencies
- Bayarcash API with a valid API token credential
Troubleshooting
- Authentication failed: Invalid or expired PAT token. Check your API credentials and renew the token if necessary.
- Validation error: The API could not process the request due to invalid parameters. Verify the filter values and formats.
- Bad request: The request was improperly formatted or contained invalid parameters. Ensure all parameters are correctly set.
- Forbidden: Access denied due to insufficient permissions or disabled payment channels. Confirm your account permissions and enabled channels.
- Not found: The requested resource does not exist. Check the transaction ID or filter criteria for correctness.
- Server error: The Bayarcash server encountered an error. Retry the request later or contact support if the issue persists.