BCL icon

BCL

Consume BCL Payment API
Join our community

Actions20

Overview

This node integrates with the BCL Payment API to create and manage payment-related resources. Specifically, for the Payment Link - Create operation, it allows users to generate a new payment link that can be shared with payers to collect payments in Malaysian Ringgit (MYR). This is useful for businesses or individuals who want to quickly generate payment requests without building a full checkout system.

Typical use cases include:

  • Sending a payment request to a customer via email or chat.
  • Creating unique payment links for invoices or orders.
  • Allowing customers to pay using various supported payment channels.

Example: A small business owner wants to send a payment link to a client for a service rendered. They specify the amount, payer details, and optionally customize the payment channel or add remarks. The node returns a payment link URL that can be sent to the client.

Properties

Name Meaning
Amount Payment amount in MYR (Malaysian Ringgit), with two decimal precision.
Payer Name Name of the person making the payment.
Payer Email Email address of the payer.
Payer Telephone Number Malaysian mobile number format (e.g., 012-3456789).
Portal Key Bayarcash Portal Key obtained from the Bayar.cash portal console.
Additional Fields Collection of optional fields:
- Order Number Unique identifier for the transaction; auto-generated if not provided.
- Payment Channel Payment channel to be used. Options include: FPX Online Banking, FPX Line of Credit, DuitNow Online Banking, DuitNow QR, SPaylater, Boost PayFlex, QRIS OB, QRIS Wallet, NETS.
- Let User Choose Payment Boolean flag to allow the user to select their payment method on the payment page.
- Remarks Remark or notes for the order.

Output

The node outputs JSON data representing the response from the BCL Payment API after creating the payment link. This typically includes details such as the generated payment link URL, transaction identifiers, status, and any other metadata returned by the API.

If an error occurs, and "Continue On Fail" is enabled, the output will contain an error object with fields:

  • error: Description of the error.
  • statusCode: HTTP status code returned by the API.
  • timestamp: Time of the error occurrence.
  • resource: The resource involved ("paymentLink").
  • operation: The operation attempted ("create").

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.
  • Users must have a valid Bayarcash Portal Key configured in the node parameters.
  • No additional external dependencies are required beyond standard HTTP connectivity.

Troubleshooting

Common Issues

  • Authentication failures: Invalid or expired API token or incorrect Portal Key will cause authentication errors.
  • Validation errors: Missing required fields or invalid formats (e.g., phone number format) may cause the API to reject the request.
  • Bad requests: Improperly formatted input or unsupported parameter values.
  • Permission errors: Insufficient permissions to access or create payment links.
  • Server errors: Temporary issues on the BCL server side.

Error Messages and Resolutions

  • Authentication failed: Check that the API token credential and Portal Key are correct and active.
  • Validation error: Review all required fields and ensure they meet the expected formats and constraints.
  • Bad request: Verify the structure and types of all input parameters.
  • Forbidden: Confirm that your account has permission to perform the requested operation.
  • Not found: Ensure referenced resources (like order numbers) exist if applicable.
  • Server error: Retry after some time or contact BCL support if persistent.

Enabling "Continue On Fail" allows the workflow to continue processing subsequent items even if one fails, with error details included in the output.

Links and References

Discussion