Himalayan Bank (HBL) 2C2P Payment Gateway Integration – WebApp Nepal
Quick answer
WebApp Nepal integrates Himalayan Bank's payment gateway so your website can accept Visa, Mastercard and Asian cards from international customers, with settlement in NPR to your HBL account.
A trekking operator based in Kathmandu had a visitor profile that most of his competitors did not yet think about systematically: Japanese trekkers. They were polite, well-prepared, booked months in advance, spent generously on equipment and premium experiences, and almost universally preferred to pay by card rather than cash or digital transfer. The problem was not finding them - Japan is one of Nepal's consistent top-five source markets for high-end mountain tourism, and his Japanese inquiry volume was growing. The problem was the payment step. His website had eSewa and Khalti, which Japanese visitors could not use without a Nepal phone number and bank account. His PayPal setup had been dormant for months because the account needed reverification. A European bank transfer took days and required his clients to navigate their bank's international wire interface. He was losing confirmed Japanese bookings at the payment stage - not to competitors, but to friction. A colleague suggested Himalayan Bank's payment gateway. He was already banking with HBL. Within three weeks his website accepted Japanese Visa and Mastercard deposits directly. The friction disappeared.
Himalayan Bank Limited - one of Nepal's earliest and most established private commercial banks, operating since 1993 - offers a merchant payment gateway service for Nepal businesses built on the 2C2P payment platform. 2C2P is a Singapore-headquartered payment technology company with deep infrastructure across South and Southeast Asia, processing card payments, regional digital wallets, and cross-border transactions for banks and merchants across Thailand, Singapore, the Philippines, Indonesia, Malaysia, Vietnam, and the broader Asian payment corridor. For Nepal businesses that bank with HBL and need international card acceptance - particularly from the growing East Asian and Southeast Asian visitor markets that 2C2P's infrastructure is specifically engineered for - HBL's 2C2P-powered gateway provides card payment capability with NPR settlement through a banking relationship that many Nepal businesses already hold.
Himalayan Bank as a Payment Gateway Issuer
Himalayan Bank Limited holds Visa and Mastercard card acquiring licences, enabling it to process card transactions on behalf of Nepal merchants and settle the proceeds to merchant accounts. HBL's merchant gateway is powered by 2C2P's payment infrastructure - a platform that distinguishes itself from Western-centric payment processors through its specific expertise in Asian payment flows, Asian card networks, and the cross-border transaction patterns relevant to Nepal's tourism, export, and diaspora commerce with Asian markets. Nepal businesses hold HBL accounts in significant numbers across the Kathmandu Valley, Pokhara, Chitwan, Biratnagar, Birgunj, and Nepal's other commercial centres. For businesses already in an HBL banking relationship, extending that relationship to include HBL's merchant payment gateway involves a more straightforward onboarding process than opening a new merchant account at an unfamiliar bank.
The 2C2P platform processes billions of dollars annually across its Asian merchant network. Its architecture reflects the specific requirements of Asian payment markets: handling high volumes of cross-border Asian card transactions, supporting the diversity of card networks active across South and Southeast Asia, and providing the fraud detection models calibrated to Asian transaction patterns - which differ meaningfully from the European and North American transaction patterns that Western payment processors use as their primary fraud model baseline. For Nepal merchants whose international buyers are disproportionately from Japan, South Korea, China, Taiwan, Hong Kong, Singapore, Thailand, and India, 2C2P's Asian-market infrastructure is not incidental - it is a technical alignment between gateway capability and Nepal's actual international visitor and buyer geography.
What 2C2P Brings to Nepal Payment Processing
Asian Card Network Coverage
Nepal's international visitor base is geographically diverse, and the card networks those visitors carry reflect that diversity. Japanese visitors carry JCB cards alongside Visa and Mastercard - JCB is Japan's domestic card network and is carried by a significant proportion of Japanese travellers. Chinese visitors on licensed tour packages may carry UnionPay cards. South Korean visitors often carry domestically-issued Korean Visa and Mastercard, as well as cards from Korean financial institutions. 2C2P's payment platform has specific expertise in these Asian card networks through its regional acquiring relationships and network partnerships. Nepal merchants processing international card payments through HBL's 2C2P gateway benefit from the acceptance logic calibrated for Asian-issued cards in a way that Western-origin gateways - designed primarily for European and North American card profiles - are not optimised to deliver.
Cross-Border Asian Transaction Authorisation
International card transactions fail for reasons that have nothing to do with the cardholder's intent to pay: the issuing bank's fraud detection system flags the transaction because the merchant's country (Nepal) is unfamiliar or associated with elevated risk in the issuer's model, the card was not pre-authorised for international transactions, or the transaction triggers a 3D Secure challenge that the checkout flow handles incorrectly. The authorisation rate - the proportion of attempted card payments that succeed - varies significantly between payment gateways because it depends on the acquiring bank's relationship with specific card networks and the sophistication of the 3D Secure implementation. 2C2P's platform is specifically optimised for cross-border Asian card authorisation, with acquiring relationships and fraud model calibrations that improve acceptance rates for Japanese, Korean, Chinese, and Southeast Asian-issued cards at Nepal merchants - cards that are underrepresented in the transaction models of European and North American payment processors.
Broad Asian Payment Method Reach
Beyond standard Visa and Mastercard card acceptance, 2C2P's platform supports an expanding range of Asian payment methods through its regional infrastructure. Depending on the specific configuration that HBL enables for Nepal merchants, this may include additional payment options relevant to specific Asian buyer segments. The architecture of 2C2P as a platform is designed for payment method extensibility - it was built in an environment where the payment method landscape across Asia is more fragmented than in Western markets, and where a single platform must handle cards, regional wallets, bank transfers, and QR payment schemes across multiple country contexts. For Nepal businesses whose international buyer mix skews toward Asian markets, this extensibility is a capability advantage over Western gateways that were designed for a more homogeneous card-payment landscape.
2C2P Integration Methods for HBL Merchants
Payment Token API with Hosted Payment Page
The standard integration method for HBL's 2C2P gateway in Nepal is the Payment Token API with hosted payment page - a two-step flow where the merchant's backend calls 2C2P's API to generate a payment token for the specific transaction (amount, currency, order reference, merchant ID), then uses that token to redirect the customer to 2C2P's hosted payment page for card entry. The hosted payment page is served from 2C2P's PCI DSS certified environment - card data is entered and processed on 2C2P's infrastructure, never the merchant's server. After transaction processing, 2C2P delivers the result to the merchant via a backend redirect and optionally via a direct server-to-server callback to the merchant's notification URL. WebApp Nepal implements the Payment Token API with correct HMAC-SHA512 request signing, order reference generation, backend result processing with signature verification, and order status management - covering the full transaction flow from payment initiation to confirmed order update.
Payment Token API with JavaScript Checkout
For Nepal merchants who need card capture embedded within their own website rather than via redirect to 2C2P's hosted page, the JavaScript checkout integration embeds 2C2P's payment form within the merchant's site using 2C2P's JavaScript SDK. The cardholder enters card details in a 2C2P-hosted payment form rendered on the merchant's page - visually integrated into the merchant's checkout design - and payment processing occurs through 2C2P's infrastructure without the customer visibly leaving the merchant's site. The JavaScript checkout option suits Nepal hospitality and tourism businesses that have invested in a specific checkout UX and need the card capture experience to feel continuous with the rest of their booking flow, rather than interrupting it with a visible redirect to a third-party payment page.
Recurring Payment and Subscription API
2C2P supports card tokenisation and recurring billing - storing a card token at initial payment and using it for subsequent charges without the cardholder re-entering card details. For Nepal businesses with subscription or instalment billing requirements - private schools with monthly fee instalment plans, membership clubs, software platforms with monthly SaaS billing to international subscribers, or trekking companies offering multi-instalment payment for high-value expedition packages - 2C2P's recurring API provides the card-on-file billing infrastructure. The token is stored on 2C2P's PCI-certified platform, not on the merchant's server, and subsequent charges are initiated by the merchant's backend without any cardholder action. WebApp Nepal implements 2C2P recurring payment for HBL merchant clients where instalment or subscription billing is a business requirement.
Critical Technical Implementation Details
HMAC-SHA512 Request Signing
2C2P requires payment requests to be signed using HMAC-SHA512 - a stronger hash function than the SHA256 used by some other gateways - applied to a specific concatenation of transaction parameters including merchant ID, payment description, amount, and currency code using the merchant's secret key. The resulting signature is submitted alongside the payment token request. 2C2P's servers verify the signature before generating the payment token; unsigned or incorrectly signed requests return an error without processing. WebApp Nepal constructs the HMAC-SHA512 signature server-side, with the merchant secret key stored in server environment variables and never exposed to client-side JavaScript or version control. The signature construction algorithm - the specific field order and encoding that 2C2P requires - is implemented against 2C2P's published specification and tested in sandbox before production deployment.
Payment Result Notification Handling
2C2P delivers payment results through two channels that must both be handled: the browser redirect (the customer is sent back to the merchant's result URL with transaction parameters) and the backend notification (2C2P posts transaction result data to the merchant's notification URL directly from 2C2P's servers). The backend notification is the authoritative payment confirmation because it arrives server-to-server, independently of whether the customer's browser successfully completes the redirect. WebApp Nepal implements both result channels: the browser redirect handler updates the UI and displays the appropriate confirmation or failure message to the customer; the backend notification handler - which validates the 2C2P notification signature before processing - updates order status, decrements inventory, triggers fulfilment, and dispatches the order confirmation email. Order fulfilment actions are idempotent, preventing double-processing if both the redirect and the notification arrive within a short window.
3D Secure Implementation for Asian Cards
3D Secure is particularly important for Nepal merchants accepting Asian-issued cards because many Asian card issuers enforce 3DS for cross-border transactions as a mandatory fraud control. A 2C2P integration that does not correctly handle the 3DS flow - where the customer is challenged for authentication by their issuing bank's 3DS system before the transaction is authorised - will produce silent authorisation failures for cardholders whose bank mandates 3DS, without giving the cardholder any useful error message or recovery path. WebApp Nepal configures 3DS handling in HBL 2C2P integrations so that the authentication step is presented correctly within the payment flow: the cardholder sees the 3DS challenge from their bank (OTP, banking app push, or biometric prompt), completes authentication, and the transaction proceeds to authorisation. Abandoned 3DS challenges - where the cardholder does not complete the authentication step - are handled with appropriate order status management and a clear customer communication.
Currency and Amount Formatting
2C2P processes transactions in the currency configured for the merchant's account - for Nepal HBL merchants, this is typically USD for international transactions with NPR settlement. The amount submitted in the payment request must match 2C2P's expected format: USD amounts in cents (integer, no decimal point), NPR amounts in paisa where applicable. Incorrect amount formatting is a common integration error that produces either transaction rejection or incorrect charge amounts. WebApp Nepal's 2C2P integrations apply correct currency formatting for every gateway call, with test coverage specifically for currency formatting edge cases - amounts in round numbers, amounts with fifty paisa, and amounts close to HBL gateway transaction limits - before production launch.
Refund and Void Processing
2C2P supports transaction reversal operations through its API: void for cancelling an unsettled transaction within the same day, and refund for returning funds to a cardholder's account after settlement. Void operations prevent the transaction from entering settlement and are available until the settlement cut-off time for the day. Refund operations credit the cardholder's card and appear on their statement within three to seven business days depending on their issuing bank - this timeframe is longer for some Asian-issued cards because of the settlement cycles of Asian card networks. WebApp Nepal builds admin-facing refund and void management into merchant platforms integrated with HBL 2C2P gateway, enabling merchant staff to initiate refunds from the platform's admin interface with full transaction audit logging - without needing direct access to HBL's merchant portal for routine refund operations.
Transaction Reconciliation Architecture
2C2P provides daily settlement reports through its merchant portal, listing all settled transactions with their reference numbers, amounts, card types, and settlement status. Reconciliation between a Nepal merchant's internal order records and the 2C2P/HBL settlement data is a daily operational requirement for any business processing more than a handful of card transactions per week. WebApp Nepal builds 2C2P transaction reference storage into the order data model from day one - every order record includes the 2C2P transaction ID, payment reference, card type, last four digits, authorisation code, and settlement status - enabling one-to-one matching between internal records and the HBL settlement report without manual cross-referencing. For higher-volume merchants, automated settlement reconciliation as a scheduled task can be built into the platform architecture.
HBL Merchant Account Setup
To access HBL's 2C2P payment gateway, a business must hold an HBL merchant current account and complete HBL's merchant gateway registration. Businesses already banking with HBL have a streamlined path to merchant gateway access because their KYC documentation is already on file with the bank. New HBL merchant applicants provide the standard Nepal commercial banking documentation: company registration certificate, PAN/VAT registration, memorandum and articles of association, board resolution appointing authorised signatories, citizenship documents of directors and authorised signatories, and a completed HBL merchant gateway application form specifying the business category, website URL, and estimated monthly transaction volume. HBL's merchant banking team assesses the application against HBL's merchant eligibility criteria - business type, transaction volume profile, and website review for e-commerce compliance - and issues 2C2P merchant credentials (merchant ID and secret key) after approval. The merchant ID and secret key are the technical credentials that WebApp Nepal uses to configure and authenticate the gateway integration. Approval timelines typically range from one to two weeks for businesses with complete documentation already filed with HBL, and two to four weeks for new HBL merchant applicants.
Settlement, MDR, and NRB Compliance
Card transactions processed through HBL's 2C2P gateway settle to the merchant's HBL current account in Nepali rupees, net of HBL's merchant discount rate (MDR). The currency conversion from USD (or the cardholder's billing currency) to NPR occurs at HBL's prevailing exchange rate at the time of settlement. The MDR structure covers the acquiring bank's processing costs, card network interchange fees (Visa, Mastercard, and other accepted networks), and the 2C2P platform fee. Specific MDR rates are agreed at merchant account opening and vary by card type (domestic, international Visa, international Mastercard), merchant business category, and anticipated monthly transaction volume - higher volumes sometimes qualify for negotiated rates. Settlement typically occurs one to two business days after the transaction date. The NPR settlement to an HBL Nepal bank account keeps the merchant's international card earnings within Nepal's NRB-regulated banking framework, eliminating the foreign exchange repatriation documentation requirements that come with settling international earnings into foreign currency accounts.
Nepal Industries Served by HBL 2C2P Gateway
Mountain and Adventure Tourism for Asian Markets
Japan, South Korea, and China are among Nepal's most consistent international visitor source markets, with Japanese and Korean trekkers having particularly strong per-visitor spending profiles on guided mountain experiences. Trekking agencies, expedition operators, and adventure tourism companies targeting these markets benefit specifically from 2C2P's Asian card acceptance optimisation - Japanese JCB-issued cards, Korean domestically-issued Visa and Mastercard, and Chinese UnionPay-networked cards are processed with the issuer-relationship quality that 2C2P's Asian infrastructure brings. WebApp Nepal builds trek booking and expedition deposit collection systems for HBL 2C2P gateway integrations with the specific checkout design considerations that Asian buyers expect: clear USD pricing with NPR equivalents, booking confirmation documentation suitable for Japanese and Korean tour coordinators, and payment confirmation emails in formats that work for Asian travel agency partner communication.
Heritage and Cultural Tourism Operators
Kathmandu Valley's heritage circuit operators - Pashupatinath temple tour specialists, Bhaktapur and Patan cultural walk companies, Boudhanath and Swayambhunath tour coordinators, and Lumbini Buddha birthplace pilgrimage package operators - draw significant visitor volume from Buddhist-majority countries in Asia: Japan, South Korea, Sri Lanka, Myanmar, Taiwan, and Thailand. These visitors arrive with Asian-issued cards and booking habits calibrated to Asian payment confirmation expectations. HBL's 2C2P gateway, with its Asian card acceptance optimisation, is a technically appropriate match for this visitor profile. WebApp Nepal builds cultural tour booking and payment flows for these operators with HBL 2C2P integration, covering the deposit-at-booking and balance-at-tour-completion payment pattern common in Nepal's cultural tourism sector.
Himalayan Wellness and Retreat Centres
Nepal's growing wellness tourism sector - yoga and meditation retreat centres in the Kathmandu Valley hills, Ayurvedic wellness resorts in Pokhara and Dhulikhel, mindfulness retreat programmes near Lumbini - attracts substantial Asian visitor interest, particularly from Japan and South Korea where wellness and spiritual tourism to Nepal has grown consistently. Retreat centres with fixed programme schedules require deposit-at-booking and balance-before-arrival payment collection from international participants. HBL's 2C2P gateway provides the card payment infrastructure for this collection from Asian participants using Japanese, Korean, and other Asian-issued cards, with NPR settlement to the retreat centre's HBL account.
Nepal Handicraft and Artisan Export Commerce
Nepal's artisan export sector - bronze and brass metalwork from Patan, Pashmina weaving from Kathmandu's Chhetrapati and Jawalakhel artisan communities, handmade paper products from Bhaktapur, Himalayan gemstone jewellery from Thamel exporters - serves international buyers from Asian markets alongside European and North American buyers. Japanese buyers have a specific and well-established appreciation for Nepali traditional crafts through Nepal-Japan cultural and development organisation networks. Korean buyers of Himalayan mineral products, Thai buyers of Nepalese religious artefacts, and Taiwanese collectors of Thangka paintings represent specific Asian buyer segments for Nepal's craft export market. HBL 2C2P gateway integration on artisan e-commerce platforms enables card payment from these Asian buyers at the checkout, without requiring them to have a Nepal digital wallet or use international wire transfer.
Himalayan Product Export - Tea, Herbs, and Nutraceuticals
Nepal's specialty tea sector - Ilam and Taplejung orthodox teas, Kanchanjungha Himalayan teas, specialty Darjeeling-adjacent high-altitude teas - has an established and growing buyer market in Japan and South Korea, where Himalayan and high-altitude tea provenance carries premium positioning. Nepal's medicinal herb and nutraceutical sector similarly exports to Japanese and Korean health product importers. B2B export invoice payment through HBL 2C2P gateway provides Japanese and Korean commercial buyers with a card payment path for import orders below bank wire transfer thresholds, with NPR settlement to the Nepal exporter's HBL account.
HBL 2C2P Gateway Integration Pricing at WebApp Nepal
HBL 2C2P gateway integration pricing at WebApp Nepal is structured by integration complexity. The Payment Token API with hosted payment page - the standard redirect-based integration with backend notification handling, signature verification, and order management - typically costs NPR 35,000 to NPR 55,000 and takes two to three weeks including sandbox testing and production deployment. The JavaScript checkout integration with embedded card form, frontend customisation, and admin refund panel costs NPR 55,000 to NPR 90,000 over three to four weeks. Recurring payment and subscription API integration for instalment billing or subscription platforms is scoped individually based on the recurring billing model requirements, typically ranging from NPR 70,000 to NPR 1,40,000. Integration as part of a new trekking, hotel, tourism booking, or e-commerce website project is included in the overall project scope rather than separately priced. All integrations include 3DS configuration, HMAC-SHA512 signature implementation, sandbox testing with 2C2P test credentials, and a pre-launch security review covering result signature validation and notification handler security.
For Nepal's trekking agencies, hospitality businesses, cultural tour operators, artisan exporters, and wellness retreat centres whose international buyer base skews toward Japan, South Korea, China, and Southeast Asia, HBL's 2C2P-powered gateway is not just a payment option - it is a payment infrastructure specifically aligned with how the Asian card-paying market actually transacts. WebApp Nepal builds the integration that puts that infrastructure to work on Nepal business websites. Contact us with your business type and international customer profile and we will assess whether HBL 2C2P gateway is the right payment infrastructure for your situation - and scope the integration correctly before development begins.
What Our Clients Say
Ready to Start
Your Project?
Tell us what you're building and we'll get back to you within a day with a clear, no-obligation quote.
Call Us
+977-9851198464
Email Us
[email protected]
Office
Ranibari, Kathmandu 44600, Bagmati Province, Nepal
Guides related to Himalayan Bank (HBL) Payment Gateway
Our Most In-Demand Services
Website Design and Development
Website design and development in Kathmandu, Nepal by WebApp Nepal: custom, mobile-friendly, SEO-optimized websites for businesses, e-commerce stores, travel companies, schools and NGOs, designed around your customers and goals, not a template.
Mobile Apps Development
Mobile app development in Kathmandu, Nepal by WebApp Nepal: Android, iOS and Flutter cross-platform apps for businesses, startups, e-commerce and on-demand services that connect you directly with customers and keep them engaged.
Software Development
Custom software development in Kathmandu, Nepal by WebApp Nepal: web applications, ERP, CRM and business management systems built around your real processes, so daily operations run faster and more reliably than with generic tools.
Frequently Asked Questions
Himalayan Bank Limited (HBL) offers a merchant payment gateway service powered by 2C2P - a Singapore-based Asian payment platform processing card payments across South and Southeast Asia. HBL's 2C2P gateway allows Nepal-registered HBL merchant account holders to accept Visa and Mastercard (and other supported card networks) from international cardholders, with transaction settlement in Nepali rupees (NPR) to the merchant's HBL current account. It is particularly well-suited for Nepal businesses serving Japanese, Korean, Chinese, and Southeast Asian buyers due to 2C2P's Asian card acceptance optimisation.
2C2P is a Singapore-headquartered payment technology company with payment processing infrastructure across South and Southeast Asia - Thailand, Singapore, the Philippines, Indonesia, Malaysia, Vietnam, and the broader Asian payment corridor. Himalayan Bank uses 2C2P as the underlying technology for its merchant payment gateway because 2C2P brings Asian card network expertise, cross-border Asian transaction optimisation, and a PCI DSS certified payment environment. For Nepal merchants whose international buyers come primarily from Asian markets, 2C2P's Asia-native infrastructure offers authorisation rate advantages over Western-origin payment processors.
The primary difference is the underlying gateway technology and its geographic optimisation. NIMB and NIC Asia bank use Cybersource - a Visa company with global processing infrastructure primarily calibrated for Western card markets. HBL uses 2C2P - an Asian payment platform with specific expertise in Japanese, Korean, Chinese, and Southeast Asian card networks and cross-border transaction patterns. For Nepal businesses whose international buyers are predominantly from Asia (tourists, diaspora buyers, export trade partners), HBL's 2C2P gateway may deliver better card acceptance rates for Asian-issued cards. Both options settle in NPR to a Nepal bank account and require a merchant account at the issuing bank.
2C2P has established relationships with Asian card networks including JCB (Japan's domestic card network, carried by a significant proportion of Japanese international travellers). Card network coverage through HBL's specific gateway configuration should be confirmed with HBL's merchant banking team at account setup, as the exact accepted networks depend on HBL's acquiring agreements. For Nepal businesses targeting Japanese visitors - trekking agencies, hotels, cultural tour operators, artisan exporters - 2C2P's Asian card network expertise makes HBL gateway the most appropriate Nepal bank-issued gateway option to explore.
2C2P has infrastructure for UnionPay transactions in its Asian regional network. Whether UnionPay acceptance is enabled for HBL Nepal merchants specifically depends on HBL's acquiring agreement configuration with 2C2P. Confirm UnionPay acceptance with HBL's merchant banking team during account setup. For Nepal businesses with significant Chinese visitor volumes - Kathmandu Valley heritage operators, Lumbini pilgrimage package companies, and Himalayan product exporters with Chinese buyers - UnionPay acceptance alongside Visa and Mastercard meaningfully extends the reachable payment market.
Yes. Card transactions processed through HBL's 2C2P gateway settle in Nepali rupees (NPR) to the merchant's HBL current account, net of HBL's merchant discount rate. The currency conversion from the cardholder's billing currency (USD, JPY, KRW, EUR, etc.) to NPR occurs at HBL's prevailing exchange rate at settlement time. NPR settlement to a Nepal bank account keeps international card earnings within Nepal's NRB-regulated banking framework without requiring foreign currency repatriation documentation.
Three 2C2P integration methods are available for HBL merchants: (1) Payment Token API with hosted payment page - backend generates a payment token, customer redirects to 2C2P's hosted card entry page, safest PCI compliance path. (2) JavaScript checkout - 2C2P's payment form embedded within the merchant's own site via JavaScript SDK, customer stays on the merchant's page throughout checkout. (3) Recurring payment API - card tokenisation at initial payment for subsequent charges without re-entry, for subscription or instalment billing. WebApp Nepal implements all three based on the merchant's UX and business requirements.
HMAC-SHA512 is a cryptographic request signing method that 2C2P requires for payment token API requests. The merchant constructs a hash using specific transaction parameters (merchant ID, amount, currency, order reference) combined with their secret key using the SHA-512 algorithm. The resulting signature is submitted with the payment request. 2C2P verifies the signature before generating the payment token - unsigned or incorrectly constructed requests are rejected. SHA-512 is a stronger hash function than the SHA-256 used by some other gateways, providing additional protection against signature collision attacks. WebApp Nepal constructs the HMAC-SHA512 signature server-side, with the merchant secret key stored only in server environment variables.
2C2P delivers payment results through two channels: (1) Browser redirect - the customer is sent to the merchant's result URL with transaction parameters after payment. (2) Backend notification - 2C2P posts the transaction result directly to the merchant's notification URL server-to-server, independently of the browser. The backend notification is the authoritative confirmation because it is not dependent on the customer's browser completing the redirect. WebApp Nepal implements both channels: the redirect handler updates the customer-facing UI, and the notification handler - after validating 2C2P's notification signature - updates order status, triggers fulfilment, and dispatches confirmation emails.
Yes. HBL's payment gateway is issued to HBL merchant account holders. Businesses must hold an HBL merchant current account. Businesses already banking with HBL have a streamlined application path as their KYC documentation is already on file. New HBL merchant applicants provide standard Nepal commercial bank documentation: company registration, PAN/VAT certificate, memorandum and articles of association, board resolution, and director citizenship documents. After KYC review, HBL issues 2C2P merchant credentials (merchant ID and secret key) required for integration.
Yes. 2C2P's recurring payment API supports card tokenisation at the initial transaction and subsequent charges using the stored token without the cardholder re-entering card details. This enables instalment billing (school tuition in monthly instalments, expedition payment across three or four instalments), subscription billing (monthly membership, SaaS platforms billing international subscribers), and card-on-file charging for repeat-purchase e-commerce. The card token is stored on 2C2P's PCI-certified platform, not on the merchant's server. WebApp Nepal implements 2C2P recurring payment for HBL merchants where the business model requires it.
Japanese and Korean trekkers represent high-value market segments for Nepal's mountain tourism sector with consistent booking volumes and high per-trip spending. Both markets have their own domestically-issued card profiles - Japanese JCB cards and Korean domestically-issued Visa/Mastercard - and both markets have high 3D Secure adoption by card issuers for cross-border transactions. 2C2P's Asian card network optimisation and cross-border authorisation expertise directly addresses these characteristics. For Nepal trekking agencies whose clients disproportionately come from Japan and South Korea, HBL 2C2P gateway's Asian infrastructure alignment makes it technically more appropriate than Western-origin gateways that were not designed for Asian card market patterns.
2C2P implements 3D Secure authentication for card transactions where the card-issuing bank requires it. Many Asian card issuers - particularly Japanese and Korean banks - mandate 3DS for cross-border online transactions. 2C2P's 3DS implementation handles both the frictionless flow (low-risk transactions authenticated without customer action) and the challenge flow (OTP via SMS, banking app push notification, or biometric prompt). WebApp Nepal configures 3DS handling in HBL 2C2P integrations so authentication challenges appear as expected, clearly communicated steps within the payment flow - reducing abandonment from customers who encounter an unexpected 3DS challenge without context.
Yes. HBL 2C2P gateway integration can be added to an existing website without rebuilding it, provided the site has appropriate backend architecture for API calls and result handling. WebApp Nepal assesses the existing site's technical stack before scoping the integration. WordPress sites receive integration via a custom backend extension. Custom-coded sites receive direct API integration. A Payment Token API with hosted payment page added to an existing site typically takes two to three weeks including sandbox testing. HBL merchant credentials (2C2P merchant ID and secret key) are required to begin development - sandbox credentials can usually be obtained before production credentials to allow development to start.
2C2P operates a PCI DSS certified payment environment. For merchants using the hosted payment page integration, card data is entered on 2C2P's PCI-certified infrastructure - not the merchant's server - reducing merchant PCI scope to SAQ A. For JavaScript checkout integration, card data is captured in 2C2P's hosted form elements (iframes) before tokenisation, similarly keeping card data off the merchant's server. WebApp Nepal does not implement HBL 2C2P integrations that route raw card data through merchant servers.
2C2P supports void and refund operations. Void cancels a transaction before settlement (same day, before cut-off time). Refund credits a settled transaction back to the cardholder's card - timeline for refund appearance on the cardholder's statement is three to seven business days for most cards, potentially longer for some Asian card networks due to regional settlement cycle differences. WebApp Nepal builds admin-facing refund management into merchant platforms, enabling staff to initiate refunds from the merchant's own admin interface with full audit logging - amount, timestamp, initiating staff member, and 2C2P refund reference.
WebApp Nepal stores the full 2C2P transaction payload against each order record: 2C2P transaction reference, payment reference, card type, card last four digits, authorisation code, response code, transaction status, amount, currency, and timestamp. No sensitive card data is stored - only the non-sensitive metadata returned by 2C2P post-transaction. This data enables reconciliation between internal order records and HBL's settlement reports, supports dispute evidence preparation, and provides the audit trail required for Nepal business accounting and NRB-compliant revenue reporting.
HBL 2C2P gateway integration pricing at WebApp Nepal: Payment Token API with hosted payment page costs NPR 35,000 to NPR 55,000. JavaScript checkout with embedded card form and admin refund panel costs NPR 55,000 to NPR 90,000. Recurring payment and subscription API integration ranges NPR 70,000 to NPR 1,40,000 based on billing model complexity. Integration as part of a new website or application project is included within the overall project scope. All integrations include HMAC-SHA512 signing, 3DS configuration, backend notification handling, sandbox testing, and security review before production launch.
Nepal businesses with significant Asian international buyer or visitor volumes benefit most from HBL 2C2P gateway: trekking agencies and expedition operators targeting Japanese, Korean, and Chinese mountain tourism markets; Kathmandu Valley heritage and cultural tour operators serving Buddhist-country Asian visitors (Japan, Korea, Sri Lanka, Myanmar, Thailand); wellness retreat and yoga centres attracting Asian wellness tourists; Nepal handicraft exporters selling to Japanese and Korean buyers; specialty tea and Himalayan herbal product exporters to Asian health markets; and hotels and resorts seeking to capture direct bookings from Asian OTA-referred guests.
Two parallel processes: (1) Contact Himalayan Bank's merchant banking team to apply for a merchant gateway account - prepare company registration, PAN/VAT, MoA, board resolution, director citizenship documents, and your website URL. HBL issues 2C2P merchant credentials (merchant ID and secret key) after KYC approval (one to four weeks). (2) Contact WebApp Nepal to scope the technical integration - we assess your website or application, recommend the appropriate 2C2P integration method, and produce a proposal with timeline and NPR pricing. Development can begin with 2C2P sandbox credentials while the production merchant account is in progress, allowing integration to be built and tested before production credentials arrive.