Bayarcash icon

Bayarcash

Consume Bayarcash API
Join our community

Actions6

Overview

This node integrates with the Bayarcash API to list transactions, allowing users to retrieve a filtered list of payment transactions processed through Bayarcash. It is useful for scenarios where you want to monitor, audit, or analyze transaction data programmatically within an n8n workflow.

Typical use cases include:

  • Fetching recent transactions filtered by status, payment channel, or other criteria.
  • Automating reconciliation processes by retrieving transaction details.
  • Integrating transaction data into reporting dashboards or CRM systems.

For example, you can list all successful transactions made via FPX payment channel or filter transactions by a specific order number or payer email.

Properties

Name Meaning
Filters Collection of optional filters to narrow down the list of transactions:
- Order Number Filter transactions by a specific order number (string).
- Status Filter transactions by status. Options: New (0), Pending (1), Failed (2), Success (3), Cancelled (4).
- Payment Channel Filter transactions by payment channel. Options: FPX (1), FPX Line of Credit (4), DuitNow Online Banking/Wallets (5), DuitNow QR (6), Boost PayFlex (BNPL From Boost) (8), QRIS Indonesia Online Banking (9), QRIS Indonesia eWallet (10), NETS Singapore (11).
- Exchange Reference Number Filter transactions by exchange reference number (string).
- Payer Email Filter transactions by payer's email address (string).

Note: The notice "These transaction endpoints are only available in Bayarcash API v3" indicates that this operation requires using version 3 of the Bayarcash API.

Output

The node outputs an array of JSON objects representing transactions matching the specified filters. Each object corresponds to a transaction record returned by the Bayarcash API and includes fields such as transaction ID, status, payment channel, order number, payer information, amount, timestamps, and other relevant metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Bayarcash API.
  • The API URL and authentication token must be configured in the node credentials.
  • The operation uses HTTP GET requests to the /transactions endpoint of the Bayarcash API v3.
  • Ensure your Bayarcash account has access to the transaction listing API and the appropriate permissions enabled.

Troubleshooting

Common issues and error messages:

  • Authentication failed: Invalid or expired API token. Verify your API key credential and refresh if necessary.
  • Validation error: The filters or parameters provided are invalid or improperly formatted. Check the filter values and ensure they conform to expected types and allowed options.
  • Bad request: The request was malformed. Review the filter parameters and their encoding.
  • Forbidden: Your account does not have permission to access this resource or the payment channel is disabled. Contact Bayarcash support or check your account settings.
  • Not found: The requested resource does not exist. This may occur if the API endpoint is incorrect or the transaction ID used elsewhere is invalid.
  • Server error: Temporary issue on Bayarcash servers. Retry after some time or contact support if persistent.

If the node is set to continue on failure, errors will be returned as JSON objects containing the error message, HTTP status code, and timestamp.

Links and References

Discussion