1 of 13

E-Commerce

Digital Payments

WooCommerce

Payments are Fragmented,

Nepali E-commerce

Shouldn’t

System Engineer @NCHL

Suraj Bhattarai

2 of 13

Fragmented Payments

Ref: https://athenaattires.com/

Checkout

Redirect

Login Credentials Fill

OTP Manually Entered

Confirmation Redirect

App/Web Based System

Social Media Sales

3 of 13

The more serious problem in multi-hop payment

The global cart abandonment rate can be seen in Nepal too . . . .

Complex checkouts, app switching, and waiting for SMS OTPs caused users to drop out right at the finish line.

70%

Source: www.statista.com

4 of 13

How is the industry fixing this issue?

CheckOut

Solution by Fonepay

Confirmation

on MoBank application of the respective Bank that uses Fonepay backed app

5 of 13

How is the industry fixing this issue?

Solution by NCHL (on web)

on ConnectIPS app

CheckOut

on Marchant’s Portal

Confirmation

on Marchant’s Portal

6 of 13

How is the industry fixing this issue?

CheckOut/Proceed

Confirmation/Reflection

Solution by NCHL (on App)

7 of 13

How is the industry fixing this issue?

Solution by NCHL (on App)

Better Implementation

with

checkout

Authentication

(Pin/Biometric)

Tokanization and e-mandate enabled

(Truely seemless)

Example: fasto.com.np

Confirmation

8 of 13

CONVINIENCE = E-Mandates

Automated Recurring Billing with e-Mandate & Tokens

Customer Subscribes → e-Mandate Auth → Token Generated → Automated Monthly Billings

WooCommerce’s native class

WC_Payment_Token woocommerce_scheduled_subscription_payment_

1.

Subscriptions, SaaS, bill payments, ISP/Cable and gym memberships in Nepal need automated recurring debits.

Automatic renewal charges

powered by Action Scheduler.

2.

PCI-compliant token storage

(No sensitive bank/card credentials stored locally).

3.

9 of 13

Never Trust the Browser (Verification & Signatures)

Flow: Securing One-Time Purchase Order Completion

Unreliable $_GET or $_POST return parameters

Always execute a mandatory server-to-server API query (GET /verify-transaction) prior to updating state.

10 of 13

add_action( 'woocommerce_blocks_payment_method_type_registration', function( \Automattic\WooCommerce\Blocks\Payments\PaymentMethodRegistry $registry ) {

$registry->register( new Your_Custom_Gateway_Blocks_Support() );

} );

What can developers & merchants build today?

Moving away from traditional custom gateways to modern WooCommerce block APIs

Example of Global experience as a reference

Optimize in-app purchase across social media

11 of 13

Preparing Your WordPress Stack for 2026+

How to upgrade your system?

Fig: Modern transition checklist for WordPress community

Leveraging headless & REST APIs

Educating clients on MSF vs. conversion:

Open Source Contribution

Sanitization &

logging gateway callbacks

Sanitization &

logging gateway callbacks

12 of 13

Interoperability between PSPs & PSOs

Universal Acceptance

​

Higher Conversion = Higher ROI

​

Future-Proofing

​

Simplicity

Way forward to

Truly unified checkout

*For NCHL Rail and channels

Any institution/person making payment

PSOs

RPS/NPI

(Open API & Routing Switch)

Non

Real-Time Switch

Real-time

Switch

fig: High-level Architecture of Retail Payment Switch

Bank Networks

NRB | Settlement

(Inter-Bank)

13 of 13

Thank You

Let’s discuss how you intend to shape e-commerce in Nepal.

Or, just leverage fintech rails?

Suraj Bhattarai

System Engineer [Infrastructure]

Nepal Clearing House Limited

/in/immrbhattarai

Disclaimer: All views, and points shared at WordCamp Kathmandu 2026 are my personal thoughts, research and voice as an individual, rather than organizational or to which I’m involved. Presentation slides are independent work too.