BCL icon

BCL

Consume BCL Payment API
Join our community

Actions20

Overview

This node integrates with the BCL Payment API to manage forms and their settings, specifically allowing you to update redirect URLs for a form. The "Update Redirect URLs" operation lets you specify URLs where users will be redirected after a payment attempt—either on success or failure.

Typical use cases include:

  • Customizing user experience by redirecting customers to specific pages after payment completion.
  • Handling different outcomes of payment attempts by directing users to success or failure pages.
  • Integrating with marketing or CRM systems by redirecting users to tailored landing pages based on payment results.

For example, after a successful payment, you might redirect users to a thank-you page, while failed payments could redirect them to a retry or support page.

Properties

Name Meaning
Form ID Numeric identifier of the form to update.
Redirect URLs Collection of URLs to set for redirection after payment:
- Success URL: URL to redirect after successful payment.
- Failed URL: URL to redirect after failed payment.

Output

The node outputs JSON data representing the response from the BCL API after updating the redirect URLs. This typically includes confirmation of the updated URLs or details about the form's current redirect settings.

The output is an array of JSON objects, each corresponding to an input item processed. Each object contains the API response data structured as returned by the BCL service.

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 BCL API endpoint at https://bcl.my/api.
  • Proper configuration of the API token credential in n8n is necessary for successful authentication.

Troubleshooting

  • Authentication errors (401): Occur if the API token is invalid or expired. Verify that the API token credential is correctly configured and active.
  • Validation errors (422): May happen if the provided URLs are malformed or missing required fields. Ensure URLs are valid and all required properties are set.
  • Bad request errors (400): Indicate improperly formatted requests or invalid parameters. Double-check property values and types.
  • Forbidden errors (403): Suggest insufficient permissions for the API token. Confirm the token has appropriate access rights.
  • Not found errors (404): Usually mean the specified form ID does not exist. Verify the form ID is correct.
  • Server errors (500+): Indicate issues on the BCL server side. Retry later or contact BCL support if persistent.

If the node is set to continue on fail, error details will be included in the output JSON for each failed item.

Links and References

Discussion