AI-Powered Financial InfrastructureGlobal PaymentsSecure & Trusted
Financial Operations · RefundsIssue refunds from the dashboard or the API, against the original payment, and track each one from request to completion alongside your settlements.
$refund = $client->refunds->create([
'payment_id' => 'pay_9F3kd82',
'amount' => 20000,
]);With Paynancial you can issue a full or partial refund against the original payment, from the dashboard or with the Refunds API, track it from request through to completion in Payment Analytics, and receive refund events by webhook.
A refund returns all or part of a payment to the customer who made it. On Paynancial, every refund is issued against the original payment, so it stays traceable to the order, booking or invoice it belongs to.
You can refund from the dashboard — useful for support teams handling one customer at a time — or from your own systems through the Refunds API, so returns and cancellations can be refunded automatically.
Locate the original payment in the dashboard, or use its payment ID in your system.
Refund the full amount, or a partial amount such as one item or a shipping charge.
From the dashboard, or with a POST to /refunds with the payment ID and amount.
A webhook tells your system as the refund changes state.
Follow the refund from request to completion in Payment Analytics.
Refunds is not a separate system — it runs through the products and tools you already use.
| Where | What you get |
|---|---|
| Dashboard | Issue a full or partial refund against a payment. |
| API | POST /refunds with payment_id and amount (in paise). See the API Reference. |
| Webhooks | Refund events as a refund changes state. See Webhooks. |
| Payment Analytics | Refund tracking and reconciliation views. See Payment Analytics. |
A plain-language guide to the frameworks that may apply. General information only. Not legal, tax, financial or regulatory advice. It is not a statement of Paynancial's own licences or authorisations.
Covers the time within which failed digital transactions — for example, a customer debited without the merchant being credited — are expected to be reversed or resolved across authorised payment systems such as UPI, cards and IMPS, and compensation to the customer when that time is missed.
Covers how authorised payment system operators and participants offer customers an online, rule-based way to raise and resolve disputes and grievances about digital payments.
NPCI's mechanism for customers to raise and track UPI complaints — such as a payment debited but not credited — from within their UPI app.
RBI's framework for payment aggregators — businesses that collect payments on behalf of merchants — covering authorisation, merchant due diligence, how merchant funds are held and settled, and grievance handling.
Regulators update these rules by circular, so always check the current text at the source: Reserve Bank of India · NPCI. For Paynancial's own security and compliance posture, see the Trust Center.
It keeps every return traceable to its order, and your reconciliation clean.
A timeout on a refund request should never turn into two refunds.
Tell customers what is refundable and how before they pay, so refunds are predictable for both sides.
Yes. Refunds can be full or partial — for example one item from an order, or a shipping charge.
Yes. Support teams can refund from the dashboard, and your systems can refund with the Refunds API by sending the payment ID and amount.
Refunds are tracked from request through to completion in Payment Analytics, and refund webhooks tell your systems as a refund changes state.
Send an idempotency key with every refund request. A retry with the same key returns the original refund instead of creating a second one.
Tell us how your business takes and moves money, and we will show you how it fits.
Discuss your payment and financial infrastructure requirements.