Hardi Jain is a product manager. This portfolio is drawn in the browser and needs JavaScript to play. You can find him on LinkedIn and GitHub.

Hardi Jain · AI and SaaS product manager

B2C · STORY 02

The purchase was ready. The payment wasn’t.

Enabling payment flexibility for high-value transactions

Transactions above ₹50,000 represented a critical segment for high-ticket merchants, but customers faced different financial constraints when completing these purchases.

01 · THE MOMENT

A high-value cart, and a payment that doesn’t fit.

Transactions above ₹50,000 represented a critical segment for high-ticket merchants, but customers faced different financial constraints when completing these purchases.

02 · THE PROBLEM

The problem wasn’t the price. It was how the price had to be paid.

Existing payment options required customers to either pay the full amount through a single instrument or finance the full principal through standard EMI.

One large purchase. Limited ways to pay for it.

03 · FINDING THE SIGNAL

The drop-off wasn’t evenly distributed.

Funnel analysis showed elevated abandonment specifically around carts above the ₹50K threshold.

Merchant tickets and user feedback pointed at the same constraint from the other side.

04 · THE INSIGHT

The customer didn’t need a cheaper purchase. They needed a different payment structure.

Payment UX is not only about reducing friction. It is about offering the right payment choice for the transaction value and customer context.

05 · THE PRODUCT QUESTION

How might we give customers more purchasing flexibility without requiring them to finance the entire amount?

Framing the question around the constraint, rather than around a feature, kept both options on the table long enough to compare them properly.

06 · THE TRADE-OFF

Two ways to structure the payment.

Standard EMI was lower effort and reused existing payment routing and partner APIs, but the customer still needed approval for the full amount, so it did not address the constraint.

DP + EMI reduced the financed principal and gave the customer control over the split, at the cost of more complex transaction routing and coordination across payment and banking integrations.

07 · THE DECISION

Don’t make the customer finance the problem.

I chose a Down Payment + EMI model that allowed customers to pay an upfront amount and finance the remaining balance through EMI.

08 · THE PRODUCT FLOW

What the customer actually experiences.

The choice had to sit inside the existing checkout, at the point where the customer was already deciding how to pay.

09 · BUILDING THE SYSTEM

A simple customer choice required a coordinated payment flow underneath.

I worked across Frontend Engineering, Backend Core Payments, Banking Partner Integration and UX Design to define and deliver the flow within a single checkout session.

10 · THE ENABLEMENT

Make the flexibility appear when it matters.

Checkout rules were configured to dynamically surface DP + EMI options when a transaction crossed the ₹50K threshold.

This wasn’t adding another payment button. It was defining when the capability should appear.

11 · THE OUTCOME

More ways to complete a high-value purchase.

High-value transactions gained a new DP + EMI payment structure.

Customers could reduce the financed principal through an upfront payment, and merchants could offer a more flexible option for high-ticket purchases.

12 · THE PRODUCT LESSON

The right payment experience changes with transaction size.

As transaction value increases, payment flexibility can become part of the product experience itself, not simply a payment-method decision.

The shape of the story

Contact me

Connecting the dots

“You can’t connect the dots looking forward; you can only connect them looking backward.”

— Steve Jobs

Map