Check what was paid against what was settled
Paymentsnp records every payment it verifies. Your provider or bank decides what reaches your account and when. Import their settlement file and every row comes back matched, missing or a different amount.
- BS dates and Nepali digits understood
- Any CSV layout, you map the columns
- Formula-safe CSV exports
| Settlement | Provider | Settled | Status |
|---|---|---|---|
| ST-2611-0012 | eSewa | 1,500.00 | matched |
| ST-2611-0013 | Khalti | 2,400.00 | mismatchVerified payment is NPR 2,450.00 |
| ST-2611-0014 | Fonepay | 800.00 | unmatchedNo verified payment with this transaction id |
| ST-2611-0009 | Khalti | 1,150.00 | reviewedChecked against the bank statement |
Verified is not settled. Two facts, from two places.
A verified payment means the provider told us the customer paid the exact amount. Settlement is the provider moving money to your bank, on the schedule and fees in your own agreement. Paymentsnp never holds the money, so it never shows a balance; it shows verified payments and helps you match them to settlement.
- Customer paysOn the provider's page
- Provider confirmsExact amount, checked by us
- Verified paymentRecorded in your dashboard
- Provider settlesTo your bank, per your agreement
- You import the fileRows matched to payments
Matching a settlement file. Export, import, review.
Download the settlement file
From your eSewa, Khalti or Fonepay merchant panel, or your bank statement.
Import it
Upload it in Reconciliation, or send rows with an API key that has reconciliation:write.
Review what does not match
Add a note to each unmatched or mismatched row once you have checked it. The row is marked reviewed and the note is kept.
| Files | Provider or bank settlement CSV, comma, semicolon or tab separated |
|---|---|
| Columns | No fixed layout; you map provider, reference, transaction id, amount and date |
| Size | Any length in the dashboard, sent in batches of 500; up to 500 records per API call |
| Dates | Gregorian or Bikram Sambat (BS) |
| Amounts | Lakh commas such as 1,50,000.00 |
| Digits | Nepali digits such as १२३ |
| Repeats | A row already imported comes back as a duplicate |
| Scope | One environment at a time, Test or Live |
Every row gets one answer. Per row, never all or nothing.
A bad row is reported on its own, so one typo does not reject the whole file.
| Status | Meaning | What to do |
|---|---|---|
| Matched | A verified payment with the same provider transaction and amount | Nothing |
| Mismatch | The payment exists but the settled amount is different | Check fees or partial settlement with the provider, then add a note |
| Unmatched | No verified payment with that transaction id | Check the environment and provider, then add a note |
| Reviewed | Someone checked an unmatched or mismatch row and left a note | Kept for the audit trail |
| Duplicate | That settlement row was imported before | Nothing; it is not counted twice |
| Invalid | The row is missing a field or has a bad value | Fix the row and import it again |
Reports your accountant will ask for. In Nepal time.
Overview
Volume, conversion, failed attempts and the split by method for any Nepal-time range up to 366 days, next to the previous period.
Provider reports
Reconciliation totals per provider for the last 7, 30 or 90 days.
CSV exports
Payments, checkouts and customers. Cells that look like formulas are neutralised, so the file opens safely in Excel.
Stuck checkouts
A list of checkouts still waiting on a provider, each with a re-check button that asks the provider again.
Refunds are recorded, not sent. The money moves in the provider panel.
Paymentsnp does not call any provider refund API. To refund a customer, refund them in your eSewa, Khalti or Fonepay merchant panel first. Then record it in the dashboard or with POST /v1/payments/:id/refunds, using the provider's refund reference.
- Refunds on a payment never add up to more than the payment.
- Each provider refund reference is recorded once per payment.
- An Idempotency-Key means a retry records the refund once.
- Every refund is audited and sends a payment.refunded webhook.
Partial or full
Record part of a payment now and the rest later, up to the payment amount.
On the payment record
Refunds sit on the payment's record, so finance sees them next to the original payment.
Automate the import. Same rules as the dashboard.
POST /v1/reconciliation/import/bulk takes up to 500 records and returns a status for each, plus counts. The key's prefix decides the environment, so a test key can never touch Live records.
GET /v1/reconciliation/report returns the 7, 30 or 90-day provider report for a key with reconciliation:read.
The SDKs call the bulk method importBulk in TypeScript and PHP and import_bulk in Python.
curl https://api.paymentnp.com/v1/reconciliation/import/bulk \
-H "Authorization: Bearer np_live_..." \
-H "Content-Type: application/json" \
-d '{
"records": [
{
"provider": "esewa",
"settlement_reference": "ST-2611-0012",
"provider_transaction_id": "000AB12",
"settled_amount_minor": 150000,
"settled_at": "2026-11-12T10:00:00+05:45"
}
]
}'
# Up to 500 records. Each row comes back with its own status:
# matched, unmatched, mismatch, duplicate or invalid.const result = await pnp.reconciliation.importBulk({
records: rows.map((row) => ({
provider: "khalti",
settlement_reference: row.reference,
provider_transaction_id: row.transactionId,
settled_amount_minor: row.amountMinor,
settled_at: row.settledAt, // ISO 8601 with offset
})),
});
console.log(result.counts); // { matched: 41, mismatch: 1, ... }# Record a refund you already made in the provider's panel.
curl https://api.paymentnp.com/v1/payments/<payment_id>/refunds \
-H "Authorization: Bearer np_live_..." \
-H "Idempotency-Key: refund-order-1001" \
-H "Content-Type: application/json" \
-d '{
"amount_minor": 50000,
"provider_refund_reference": "RF-20261112-01",
"reason": "One item out of stock"
}'Questions merchants ask. About reconciliation.
Does Paymentsnp show my balance?
No. Paymentsnp never holds your money, so there is no balance to show. Your provider or bank shows what has settled; Paymentsnp shows verified payments and helps you match the two.
Which file formats can I import?
CSV settlement files from your provider or bank. Dates in BS, amounts with lakh commas and Nepali digits are understood. Rows can also be sent as JSON through the API.
Why is a row a mismatch?
The provider settled a different amount than the verified payment, for example after fees or a partial settlement. Check it with the provider and add a review note.
Can Paymentsnp refund my customer?
No. Refund the customer in your provider's panel, then record it in Paymentsnp so your records and webhooks stay correct.
Can I see a date range in Nepal time?
Yes. Ranges follow Nepal midnight, can cover up to 366 days and show the previous period of the same length for comparison.