AI-Powered Financial InfrastructureGlobal PaymentsSecure & Trusted

Embedded Finance · Embedded Payments

Take payments inside your own product — not on someone else's page.

Technology partners embed Paynancial's Payment API directly in their software, build their own checkout on top of it, and get a real-time status and a webhook for every payment.

Ask about availability See the Payments API

Payment API
Custom or hosted checkout
Real-time status
Payment webhooks

Creating a payment from your platform

$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

Overview

What embedded payments mean on Paynancial.

Embedded payments means a platform's users pay inside the platform itself. On Paynancial, technology partners — SaaS platforms and marketplaces — embed the Payment API directly, build a custom checkout on top of it or use the hosted checkout, accept cards, UPI, netbanking and wallets, and receive a real-time status and payment webhook for every transaction. Onboarding a platform's own users as separate merchants is not described on this site; ask our team.

A booking platform that lets its customers pay without leaving the booking flow, or a vertical SaaS product that lets each of its business users take card and UPI payments inside the software they already use — that is embedded payments. The payment stops being a separate step on a separate site.

On Paynancial, technology partners embed the Payment API directly. You can build your own checkout UI on top of the API or use the hosted checkout from the Payment Gateway, and every payment returns a real-time status and a webhook your product can act on.

Availability: Embedded Payments is not described as a separate Paynancial product. This page covers what is published: technology partners embedding the Payment API, and the Partner Hub for enrolling customers.

Confirm with our team before you plan:

Onboarding your platform's users as merchants
How funds and responsibilities are split between you and your users
Pricing for platforms
Which checkout experience fits your product

How it works

Step by step.

01
Get a sandbox key
Build against the API with no real funds involved.
02
Create the payment
Call the Payments API from your product with the amount, currency and your own reference.
03
Show your checkout
Build your own checkout UI on the API, or send the customer to the hosted checkout.
04
Confirm by webhook
Mark the order paid when the payment webhook arrives.
05
Reconcile
Every transaction is tied to a settlement record you can reconcile against.

Published today

What you can build on now.

Payment Gateway and Partner Hub capabilities — not a separate embedded product.

Payment API: Create payments from your own software, with API keys and idempotent requests.
Custom checkout: Build your own checkout UI on top of the API, inside your product's design.
Payment methods: Cards, UPI, netbanking and wallets through one integration.
Real-time status: A status for every transaction, and a payment webhook as it changes.
Partner Hub: Partners can enroll customers, submit KYC, track approvals and monitor transactions.
Settlement records: Each transaction is tied to a settlement record for reconciliation.

Where it lives

Across the Paynancial platform.

Embedded Payments is not a separate system — it runs through the products and tools you already use.

Embedded Payments across Paynancial
Where	What you get
Payment Gateway	Methods, hosted or custom checkout. See Payment Gateway.
Payments API	`POST /payments`. See the API Reference.
Partner Hub	Enrolment, KYC submission and approvals. See Partners.
Webhooks	Payment events for your product. See Webhooks.

In India

Embedded payments in India.

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

UPI inside your flow: Customers in India expect to pay by UPI. Offering it inside your product, next to cards and netbanking, keeps them from dropping out.
Merchant due diligence: RBI's payment aggregator framework covers due diligence on businesses taking payments. Separately, the Partner Hub includes a KYC step.
No stored card numbers: Under card-on-file tokenisation, platforms should not store customers' actual card numbers.
Rupees and paise: The API takes amounts in paise for INR — 50000 is ₹500.00.

Compliance in India

The RBI and NPCI rules around embedded 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

Know Your Customer (KYC) Direction

Customer due diligence obligations for RBI-regulated entities. Payment aggregators apply due diligence to the merchants they onboard.

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

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.

Act of Parliament

Digital Personal Data Protection Act, 2023

India's law on processing digital personal data — including the personal data in payment records — based on consent, purpose limitation and security safeguards.

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.

Good practice

Getting it right.

01
Never trust the redirect
Confirm a payment from the webhook, not from the customer returning to your page.
02
Use your own reference
Pass your order or booking ID as the receipt, so every payment maps back to your records.
03
Keep card data out of your systems
Let the checkout handle card details, so your platform never stores them.

FAQ

Embedded Payments questions.

What are embedded payments?

Payments a platform's users make inside the platform itself, instead of on a separate provider's page — for example, paying inside a booking flow or a business software product.

How do platforms embed payments with Paynancial?

As technology partners: they embed the Payment API directly, build their own checkout UI on top of it or use the hosted checkout, and receive a real-time status and payment webhook for every transaction.

Which payment methods can my platform accept?

Cards, UPI, netbanking and wallets, through one integration with the Payment Gateway.

Can my platform onboard its own users as merchants?

Onboarding a platform's users as separate merchants is not described on this site. Partners can enroll customers, submit KYC and track approvals in the Partner Hub; ask our team about your platform's model.

Ask about embedded payments.

This capability is not confirmed as a Paynancial product. Tell us what you need and our team will tell you what is available.

Ask about availability Explore all products