Install
This is the repository archive. It installs, but the folder name will carry the branch suffix and updates will not flow.
Install straight from GitHub with WP-CLI:
wp plugin install https://github.com/hamzaamireh/cliqjo/archive/refs/heads/main.zipNo built-in updater. New versions won't appear under Dashboard → Updates. Install new releases yourself, or let Git Updater track the repository.
A WooCommerce payment gateway integrated with Bank Al Etihad's CliQ network, allowing customers to pay instantly using their CliQ Alias.
Features
- Secure checkout using native WooCommerce UI.
- Compatible with the new Cart & Checkout Blocks in WooCommerce.
- Fully authenticated via OAuth2 Client Credentials for merchant API calls.
- Dedicated configuration panel within WooCommerce Payments dashboard for TLS configuration and file uploads.
Merchant Setup & Configuration
- Open a Merchant Account with Bank Al Etihad.
- Request access to their CliQ Payment APIs.
- You will receive:
- Client ID & Client Secret
- Target Environment URLs (Token & Base API)
- A
.crtsigned TLS Certificate and your.keyfile.
- Install and activate this plugin in WordPress.
- Go to WooCommerce > Settings > Payments > Sugarbyte Payment Gateway with CliQ:
- Fill in the required endpoints.
- Upload your signed certificate
.crtand server key.keyfiles directly. - Activate the gateway.
Troubleshooting Tips
- Connection Refused / Failed to retrieve token: Ensure your server's IP address is whitelisted by Bank Al Etihad.
- Certificate Errors: Check if the uploaded
.crtmatches the provided.key. Your provider may require the certificate to be combined with a CA bundle. If so, contact your Bank Al Etihad support representative for assistance preparing a standard PEM bundle. - 400 Bad Request during checkout: Verify that the cart total and currency configuration matches what Bank Al Etihad expects, and that the CliQ alias provided by the customer is active.
Developers & Contribution
For code modifications, note that the codebase has been structured keeping WordPress official repo guidelines in mind. Ensure you sanitize inputs using functions like sanitize_text_field and escape outputs via esc_html__() before submitting PRs.