BCL icon

BCL

Consume BCL Payment API
Join our community

Actions20

Overview

This node integrates with the BCL Payment API to manage payment-related resources such as payment links, forms, and coupons. Specifically, for the Payment Link resource and the Get Transaction operation, it retrieves detailed transaction information using an order number.

This functionality is useful in scenarios where you need to verify or audit payment transactions by their unique order numbers. For example, after a customer completes a payment via a payment link, you can use this node to fetch the transaction details to confirm payment status, amount paid, payer information, and other metadata.

Practical examples:

  • Fetching transaction details to update order status in your CRM or ERP system.
  • Verifying payment success before granting access to digital content or services.
  • Auditing payments for reconciliation purposes.

Properties

Name Meaning
Order Number The unique order number identifying the transaction to retrieve. This is required to fetch the specific transaction details.

Output

The node outputs JSON data representing the transaction details retrieved from the BCL Payment API. The structure typically includes fields such as transaction ID, order number, payment status, amount, payer information, timestamps, and other relevant metadata returned by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an API token credential for authenticating with the BCL Payment API.
  • The node makes HTTP requests to the base URL https://bcl.my/api.
  • Proper configuration of the API token credential within n8n is necessary for successful authentication.

Troubleshooting

  • Authentication failed: If the API token is invalid or expired, the node will return an authentication error. Ensure that the API token credential is correctly configured and active.
  • Validation errors: If the provided order number is missing or malformed, the API may respond with validation errors. Verify that the order number is correct and properly formatted.
  • Not found errors: If the order number does not correspond to any existing transaction, a "Not found" error will be returned. Confirm the order number exists in the BCL system.
  • Server errors: Temporary server issues on the BCL side may cause 5xx errors. Retry later or contact BCL support if persistent.
  • When errors occur, if the node is set to continue on fail, it outputs an error object with details including status code and message.

Links and References

Discussion