I recently installed the Nhooja Himalayan Bank Payment plugin and would appreciate some guidance on how to set it up and use it properly. Specifically, I would like to understand:
How to configure the plugin settings
What credentials or API keys are needed from Himalayan Bank
How the payment process works for users
Any documentation or step-by-step guide available
Could you please provide instructions or point me to any relevant documentation or support resources?
Thank you for your interest in the Himalayan Bank Payment Gateway plugin. Below are answers to your questions, based on the plugin details and FAQs:
1. How to configure the plugin settings
Once you’ve installed and activated the plugin:
Go to your WordPress Dashboard → WooCommerce → Settings → Payments
Locate Himalayan Bank Payment Gateway in the list of available payment methods.
Click “Manage” to open the settings page.
Fill in the required fields such as:
Merchant ID
Encryption Key
Access Token
Toggle the Test Mode if you’re using a test account.
Turn off 3D Secure if you are using test mode
Click Save Changes to apply the configuration.
2. What credentials or API keys are needed from Himalayan Bank
To use this plugin, you’ll need to contact Himalayan Bank and request access to their HBL eCommerce Payment Gateway. Specifically, you will need the following credentials from the bank:
Merchant ID
Encryption Key
Access Token
PACO Signing Public Key
PACO Encryption Public Key
These credentials are unique to your business and are required to connect your site to the bank’s secure payment system.
3. RSA Key Generation (Required)
The plugin requires RSA encryption for secure communication with the bank. Follow these steps: 🔐 Generate your RSA Key Pair:
Keep the Private Keys securely and paste them in the corresponding fields in the plugin settings.
Send the Public Keys (encryption and signing) to Himalayan Bank.
This allows secure two-way encryption and signing of transaction data.
5. How the payment process works for users
Here’s how the user payment flow works:
A customer selects items and proceeds to checkout on your WooCommerce site.
On the checkout page, they select Himalayan Bank (HBL) Payment.
Upon submitting the order, they are redirected to the HBL Payment Gateway.
The customer enters their card details and completes the payment on HBL’s secure page.
After payment, the user is redirected back to your website with confirmation of the transaction.
The WooCommerce order status is updated accordingly based on the payment result (e.g., success or failure).
6. Any documentation or step-by-step guide available
At the moment, detailed external documentation is not listed directly on the plugin page. However, the setup is straightforward and covered under the FAQ section on the plugin page.
I’ve followed the steps shown here and it is not working. I am working with HBL to try and get it functioning but they are also unsure. I am receiving no errors on dev console, only “Oops! Something went wrong with your payment.” It’s not in test mode and all the configurations seem right. The issue persists despite removing all plugins but woocommerce, reverting theme to default and clearing all custom css. I have tried reverting to slightly earlier php versions with no success. only one slightly relevant error in debug.log
“PHP Deprecated: Return type of Carbon\Traits\Date::createFromTimestamp($timestamp, $tz = null) should either be compatible with DateTime::createFromTimestamp(int|float $timestamp): static, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/customer/www/kailashblades.com/public_html/wp-content/plugins/nexhbp-himalayan-bank-payment-gateway/vendor/nesbot/carbon/src/Carbon/Traits/Timestamp.php on line 29”
Is this plugin currently working okay for other installations? Or perhaps it is out of date?
Plugin is still working for all other installations.
“PHP Deprecated: Return type of Carbon\Traits\Date::createFromTimestamp($timestamp, $tz = null) should either be compatible with DateTime::createFromTimestamp(int|float $timestamp): static, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/customer/www/kailashblades.com/public_html/wp-content/plugins/nexhbp-himalayan-bank-payment-gateway/vendor/nesbot/carbon/src/Carbon/Traits/Timestamp.php on line 29”
It is deprecation notice. Not an error.
Make sure you are running website in PHP 8.2 or above
Hey there Sachit- thanks very much for your reply 🙂 We are in PHP 8.4.7. all plugin configurations have been triple checked Can you provide any advice on why I might be getting this error? I have taken the website out of maintenance mode for you- if you’d like to take a look it would be greatly appreciated.
Aside from this suggesting the keys are the issue can you clarify what keys or in which manner they are failing? Himalayan Bank Tech support need all the help they can get :S
Managed to get another HBL payment gateway plugin working. Moving those identical configuration details over to this one didn’t get this one working- hopefully this info helps troubleshoot problems in future 🙂
Thank you for the update, and I really appreciate you taking the time to test things and share your findings!
It’s helpful to know that you got another HBL payment gateway plugin working using the same configuration details. Since our plugin is working fine on other websites, this might point to likely configuration issues.
I’m also about to share a screenshot of the configuration that works on another site (with sensitive keys redacted), which might help spot any subtle differences.
The Encryption Key (starts with 19f84b5655f04 …….),
PACO Signing Public Key (starts with MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAr0XW6QacR8GilY4nZrJZW40wnFeYu7h9aXUSqxCP6djurCW …………………………………) , and
PACO Encryption Public Key (starts with MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEA6ZLups2K0iYEMxQqgASX8gY6tWhNVCp08YuDgjCsOVrGVgUHD0dh0TWFNJ7Lq2Jp0SOsGgi54+hrjwPOL2 …………………………………..)
Make sure 3D Secure is enabled
Make sure Test Mode is disabled
…are the same for all accounts.
However, your Merchant Signing and Encryption Public/Private Keys are generated by you. Once you provide those keys to HBL, they will provide your Merchant ID and Access Token.
Thanks again for your message and for helping improve the plugin! 😊
This reply was modified 11 months, 1 week ago by Sachit Tandukar.
Key already includes PEM headers. If the stored key already has —–BEGIN RSA PRIVATE KEY—– and —–END RSA PRIVATE KEY—–, it gets double-wrapped, which is invalid. Enter key without any headers: —–BEGIN RSA PRIVATE KEY—– and —–END RSA PRIVATE KEY—–
The key may be truncated or contain invalid characters.
Getting errors in test mode. how to fix it? 2025-12-04T05:02:38+00:00Error Client error: POST https://core.demo-paco.2c2p.com/api/1.0/Payment/prePaymentUi resulted in a 400 Bad Request response 2025-12-04T05:02:38+00:00Error #0 /home2/gzzmpcmy/public_html/wp-content/plugins/nexhbp-himalayan-bank-payment-gateway/vendor/guzzlehttp/guzzle/src/Middleware.php(72): GuzzleHttp\Exception\RequestException::create(Object(GuzzleHttp\Psr7\Request), Object(GuzzleHttp\Psr7\Response), NULL, Array, NULL)
Viewing 10 replies - 1 through 10 (of 10 total)
The topic ‘Help Needed: How to Use the Nhooja Himalayan Bank Payment Plugin’ is closed to new replies.
