AI-Powered Financial InfrastructureGlobal PaymentsSecure & Trusted

Developers · Payment APIs

Payment APIs: accept money from inside your own product.

Create payments, share payment links, collect on a schedule and refund — all from one REST API, with a real-time status and a webhook for every transaction.

Request Sandbox Access Full API Reference

Payments
Payment links
Collections
Refunds

Create a payment

$payment = $client->payments->create([
    'amount'   => 50000, // in paise
    'currency' => 'INR',
    'receipt'  => 'order_rcpt_101',
]);

echo $payment->id;

const payment = await client.payments.create({
  amount: 50000,
  currency: 'INR',
  receipt: 'order_rcpt_101',
});

console.log(payment.id);

curl https://api.paynancial.com/v1/payments \
  -u YOUR_API_KEY: \
  -d amount=50000 \
  -d currency=INR \
  -d receipt=order_rcpt_101

The APIs

Five resources for money coming in.

Every call goes to https://api.paynancial.com/v1, authenticated with your API key. Each resource powers a Paynancial product you can also use from the dashboard.

Paynancial Payment APIs
Resource	Endpoint	What it does	Product
Payments	`POST /payments`	Create a payment to accept money from a customer.	Payment Gateway
Refunds	`POST /refunds`	Refund all or part of an existing payment.	Refunds
Payment Links	`POST /payment_links`	Create a shareable link a customer can pay without a checkout on your site.	Payment Links
Collections	`POST /collections`	Collect recurring or scheduled payments from a customer.	Smart Collections
Transaction reports	`POST /reports/transactions`	Generate a transaction report for a date range, for your finance team or accounting system.	Payment Analytics

Which API

Pick the call that matches the job.

Choosing a Payment API
When you need to…	Use
Charge a customer at checkout in your website or app	Payments
Get paid without a checkout — on an invoice, by email or message	Payment Links
Charge the same customer every month, or in instalments	Collections
Give money back, in full or in part	Refunds
Hand your finance team a period's transactions	Transaction reports

Payment lifecycle

From API call to settled money.

What happens to a payment you create, and where your code comes in.

01
Create
Your server creates the payment with an amount, currency and your own receipt reference, and reads its id.
02
Checkout
The customer pays on the hosted checkout, or on a checkout UI you build on top of the API — by card, UPI, netbanking or wallet.
03
Status
Paynancial returns a real-time status for the transaction.
04
Webhook
A payment event reaches your webhook endpoint. Fulfil the order here, not on the customer's redirect.
05
Settled
The transaction is tied to a settlement record you can reconcile against — and refunded through the Refunds API if needed.

Create a payment

The parameters in the published example.

Payments parameters
Parameter	Meaning
`amount`	Amount in the smallest currency unit (paise for INR) — 50000 is ₹500.00
`currency`	Currency code, e.g. INR
`receipt`	Your own reference for the order

A payment object; the examples read its id. For other parameters, see the API Reference or ask developer support.

Create a payment link for an invoice

$link = $client->paymentLinks->create([
    'title'    => 'Invoice #204',
    'amount'   => 500000, // in paise, or omit to let the customer enter it
    'currency' => 'INR',
]);

echo $link->short_url;

curl https://api.paynancial.com/v1/payment_links \
  -u YOUR_API_KEY: \
  -d title='Invoice #204' \
  -d amount=500000 \
  -d currency=INR

Reliability

Build it so nothing is charged twice or missed.

Idempotency keys: Send an idempotency key on every create call. A retry with the same key returns the original result instead of creating a duplicate.
Webhooks, not redirects: Customers close tabs and lose signal. The payment webhook is the reliable signal that money arrived.
Structured errors: An error code such as invalid_method tells your code whether to fix the request or retry; rate_limited means back off and retry with the same key.
Sandbox, then live: Build and test with a sandbox key and no real funds, then switch to a live key. Nothing else in your code changes.

Webhooks → Authentication →

In India

Accepting payments from customers in India.

General information only. Not legal, tax, financial or regulatory advice.

Amounts in paise: The API takes amounts in the smallest currency unit — 50000 is ₹500.00. Never send rupees with decimals.
UPI alongside cards: UPI sits next to cards, netbanking and wallets at checkout; many customers in India reach for it first.
No stored card numbers: Under RBI's card-on-file tokenisation rules, your systems should not store customers' actual card numbers — let the checkout handle card details.
Recurring needs a mandate: Recurring card and UPI payments typically run on an e-mandate the customer registers, with a notice before each debit.

Compliance in India

The RBI and NPCI rules around accepting payments in India.

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.

RBI

Payment Aggregator and Payment Gateway guidelines

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.

RBI

Card-on-File tokenisation

Covers card-on-file tokenisation: a card saved for repeat payments is replaced by a token, created with the customer's consent, instead of the actual card number being stored.

RBI

E-mandates for recurring payments

Covers e-mandates for recurring payments on cards, UPI and prepaid instruments, including registration by the customer with additional authentication, a notification before each debit, and the option to withdraw the mandate.

RBI

Turn Around Time (TAT) for failed transactions

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.

RBI

Digital Payment Security Controls

RBI's expectations for governance, secure application design, authentication and fraud-risk monitoring in digital payment products offered by regulated entities.

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.

FAQ

Payment API questions.

What are the Paynancial Payment APIs?

The money-in resources of the Paynancial REST API: Payments, Payment Links, Collections, Refunds and transaction reports. Every call goes to https://api.paynancial.com/v1 and is authenticated with your API key.

Which API should I use to charge a customer?

Payments for a checkout in your own website or app, Payment Links to get paid without a checkout, and Collections for recurring or scheduled charges. Refunds give money back, in full or in part.

How do I know a payment succeeded?

Each transaction returns a real-time status, and a payment webhook reaches your endpoint as it changes. Fulfil orders on the webhook, not on the customer's redirect.

What currency unit does the API use?

The smallest currency unit — paise for INR — so 50000 is ₹500.00.

Make your first payment in the Sandbox.

Request a sandbox key and create a test payment with no real money involved.

Request Sandbox Access Contact Developer Support