Provider Fees

How PayBridgeNP tracks and surfaces the fee each payment provider charges, and how to set your negotiated eSewa rate.

PayBridgeNP records the provider fee on every successful payment so you can see exactly how much each provider charges, broken down by provider, on your dashboard. Each provider exposes fee information differently - here’s how each one works.

At a glance

Provider	Fee source	Merchant config
Khalti	Reported live by Khalti’s API on every payment	None - read automatically
eSewa	Computed from your saved rate × payment amount	Set your rate on Providers
Fonepay	Free	None - always 0

Khalti

Khalti returns the per-transaction fee in its lookup response. We read it on every successful payment and persist it to the payment row. No merchant configuration needed.

eSewa

eSewa does not expose per-transaction fees on its API. To track fees for eSewa, you tell PayBridgeNP what rate you have negotiated with eSewa, and we compute the fee at payment time.

Set your rate

1. Go to Providers in the dashboard
2. Find the eSewa card
3. Type your negotiated rate (in percent) into the Provider fee input
4. Click Save

The default is 1.5% - a reasonable public-rate fallback. If your real rate is different, set it before relying on the fee numbers.

How it’s computed

For each successful eSewa payment:

fee_paisa = round(amount_paisa × fee_bps / 10000)

Where fee_bps is your saved rate in basis points (150 = 1.50%, stored on provider_credentials.fee_bps). The rate at the time of payment is snapshotted into payment.metadata.esewa_fee_bps so historical totals stay correct even after you change the rate later.

Fonepay

Fonepay does not charge a transaction fee. Every Fonepay payment is tagged with fonepay_fee_paisa = 0 so the dashboard renders “Free” consistently with the other providers.

Where you see it

• Dashboard home - a “Provider fees” KPI card next to Volume, Payments, and Success rate, plus the period’s effective rate.
• Provider breakdown - fee total and effective rate per provider on the dashboard home.
• Payments list - a Fee column on every payment row.
• Payment detail - a Provider fee line, with your eSewa rate shown as a tooltip.
• CSV export - a Provider Fee (NPR) column on the Payments export.

API access

If you consume payment data via the API (or webhooks), the fee surfaces on payment.metadata with stable keys:

Key	Type	Set on
khalti_fee_paisa	integer (paisa)	Successful Khalti payments
esewa_fee_paisa	integer (paisa)	Successful eSewa payments
esewa_fee_bps	integer (basis points)	Successful eSewa payments - snapshot of your rate at the time
fonepay_fee_paisa	integer (paisa)	Successful Fonepay payments - always 0

Refunded payments do not contribute to fee totals - when a payment is fully refunded, its status flips to refunded and it is excluded from the dashboard’s fee aggregates. This matches reality: providers typically refund their fee alongside the principal.

Caveats

• Fee tracking started on 2026-04-29. Payments before that contribute 0 to fee totals - they were not captured at write time.
• The eSewa fee is only as accurate as the rate you save. If you renegotiate with eSewa, update the rate on the Providers page so your dashboard reflects reality going forward.
• Partial refunds are not counted against fees in aggregate (PayBridgeNP does not track partial refunds in its payment status enum). If you issue many partial refunds, your dashboard fee total will slightly overstate what the provider actually kept.