COMMERCE & WORKFLOWS / 2026

FynixThe quote, the charge, the invoice. In agreement.

Checkout edge cases, referral controls, tax-aware invoicing, and recovery workflows.

My focus
Checkout correctness, invoicing & registration tooling
Working with
Next.js · TypeScript · Razorpay · Transactions
THE OUTCOMEOne consistent amount
Explore my contribution
FYNIXCONCEPTUAL FLOW
Commerce & workflows
  1. 01Quote
  2. 02Reserve
  3. 03Verify payment
  4. 04Invoice
2026CONTEXT / DECISIONS / DETAILS
01 / THE CONTEXT

The quote, the charge, the invoice. In agreement.

The Fynix work includes an event-registration and payment journey with country-based pricing, referral codes, invoicing, and administrative recovery.

The problem to work through

A large referral discount could create an order below the payment provider’s minimum. A currency-related payment decline also exposed internal error wording that gave the buyer no useful next step.

02 / MY CONTRIBUTION
01

Keep one price through the flow

I capped the discount percentage before the order was created so the quote, stored order, and rebuilt invoice continue to agree. The documented USD example changed a 99% discount to an effective 98% discount.

02

Explain an actionable retry

I replaced an opaque payment-failure message with a conditional country-and-currency hint, keyed to the order currency. The message does not pretend to know where the card was issued.

03

Operational tools

My work also covered tax-aware invoicing, referral limits, registration tooling, and manual recovery paths.

03 / THE OUTCOME

One consistent amount

In the documented checkout case, the adjusted discount produced a $1.98 charge above the provider minimum. This is an example from that fix, not pricing guidance.

What I take from it

Payment UX depends on the data model. Keeping one stored discount driving the quote and invoice prevents a friendly interface from promising the wrong amount.

04 / EXPLORE THE EVIDENCE
CONTINUE EXPLORINGGKR HospitalityWeb experience