- Account
- ••••4821
- IFSC
- DEMO0001234
- Holder
- Demo Pvt Ltd
- Use
- Payouts
Peneu platform
Payment Orchestration Platform
One Integration. Multiple Payment Providers. Intelligent Routing.
Merchants connect once. Peneu watches each provider, routes every payment by your rules, moves it when a provider fails, and keeps one record across banks, rails, payouts and payments from abroad.
Payment trace PAY-DEMO-7F21
- Received
- Routed
- Failover
- Authorised
- Webhook
- Reconciled
Provider health EXAMPLE
- Provider AACTIVE Available Unavailable
- Provider BACTIVE Available
- Provider C Degraded
Routing
Provider A → ActiveUPI follows your rule: Provider A first.
Route updated → Provider BProvider A is unavailable, so the payment moves to B.
UPI: A → BCards: B → AIntl cards: C
Event stream
- payment.createdSent from the merchant’s checkout
- Health observedProviders A, B and C checked
- Route selectedProvider A, by your rules
- Provider unavailableProvider A stopped responding
- Route updatedPayment moved to Provider B
- payment.authorizedProvider B approved it
- Webhook deliveredpayment.authorized sent to you
- NormalisedOne record format, any provider
- ReconciledMatched to the settlement line
A simulated payment, not live data. Provider names, rules and events are examples.
The orchestration layer
Ten capabilities, in three layers
Connect your providers once, decide where each payment goes, and run the operation afterwards. Each capability has its own page with how it works, what you can configure and where its limits are.
Your checkout, app or platform
01
Connect
One integration in front, several providers behind it, one API and one event stream.
02
Decide
Where each payment goes, what happens when it fails, and when a provider is taken out.
03
Operate
Money reconciled across providers, and customers paying from abroad.
Payment providers, banks and rails
Payment transaction trace
Follow one payment from checkout to the settlement file
Every step leaves a record under the same reference, so when a customer asks where their money is, you can answer from one screen instead of three provider dashboards.
- MerchantCheckout sends the payment request
- PeneuChecks provider health and your rules
- ProviderTakes the payment from Peneu
- AuthorisationThe bank or network approves or declines
- PaymentMarked paid, under one reference
- WebhookYour server hears the outcome
- ReconciliationMatched against the settlement
An illustrative trace. Which provider handles a payment, and how fast each step is, depends on your setup.
Provider network
Several providers, one set of routing rules
Each connection reports its health. When one stops answering, its traffic moves to the next eligible provider, and moves back once it recovers.
Payment connections ILLUSTRATIVE
- AProvider A ROUTEDUPI · Cards · Netbanking● Available● Unavailable● Recovering
- BProvider B ROUTEDUPI · Cards · Wallets● Available
- CProvider CCards · International cards● Degraded
Routing
UPIProvider A, then BCardsProvider B, then AInternational cardsProvider C
Routing UPI to Provider A, as your rules say.
Routing updated. Provider A is unavailable, so UPI goes to Provider B.
Provider A recovering. Traffic shifts back as it proves healthy.
Rules and providers are examples. Which providers you connect is confirmed during onboarding.
Payments
Take payments by every method your providers support
UPI, cards, netbanking, wallets and international cards, through one integration. Payment links, UPI AutoPay and mandates run on the same connections.
Payment Gateway UPI & QR Collection API Payment Links Refund API
A UPI or QR payment, step by step
- CustomerPicks UPI, or scans the QR
- UPI / QRThe request reaches the customer’s UPI app
- PeneuRoutes it to the provider your rules pick
- ProviderCollects the payment over UPI
- Payment confirmationApproved, or moved to another eligible provider
- WebhookYour server hears the result, in one format
Which methods and providers are live for your business is confirmed during onboarding.
Payouts and banking
Send money out on the right rail, and know where each payout stands
Payouts go by IMPS, NEFT, RTGS or UPI depending on amount and urgency. Every payout carries a status you can act on, including the ones that aren't final yet.
Payouts Bulk payouts Virtual accounts API banking Settlement
- Account
- ••••0937
- IFSC
- DEMO0005678
- Holder
- Demo Pvt Ltd
- Use
- Collections
| Payout | Rail | Status |
|---|---|---|
| PO-DEMO-0141 | IMPS | Processed |
| PO-DEMO-0142 | UPI | Processing |
| PO-DEMO-0143 | NEFT | Pending |
| PO-DEMO-0144 | IMPS | Reversed |
Accounts, IDs and statuses are illustrative.
A payout, start to finish
Payout request Peneu UPIIMPSNEFTRTGS Bank
- QueuedAccepted, waiting its turn
- ProcessingSent to the bank on the chosen rail
- ProcessedFinal: the money reached the account
- Pending
No final answer yet. Wait, don't resend. - Failed
Final. Fix the reason, then pay again. - Reversed
Returned after it was sent.
The rail follows amount and urgency; RTGS is for ₹2 lakh and above. Status names follow the payouts guide.
Verification and KYC
Check accounts, identities and businesses before money moves
The checks sit on the same platform as payments and payouts, so a payout can wait for its account check and onboarding can wait for KYC.
Verify Bank account
Check an account exists and whose it is before you pay into it.
Account ••••0192IFSC DEMO0001234Account active · name matches
Verify Aadhaar
Offline methods, with the holder's consent.
Aadhaar XXXX XXXX 1234Shared by holder with consent
Verify GSTIN
Check a GSTIN is active and see its registered name.
GSTIN 27AAAAA0000A1Z•Active · legal name returned
Verify KYC
Layered identity checks for onboarding customers.
Customer DEMO-C-22173 checks passed · 1 to review
Verify KYB
Registrations, people and bank account for a business.
Business Demo Pvt LtdRecords agree · 1 to review
Inputs are masked examples and results are illustrative, not guarantees of what any check will return.
Recharge and bill payments
Recharges, FASTag and BBPS bills from the same platform
For apps and retail counters that let customers top up and pay bills. Each category runs through the service built for it.
RechargesRecharge API
Categories are the kinds BBPS covers in general; which categories, billers and operators are reachable through Peneu is confirmed during onboarding.
Global payments
Accept payments from customers abroad, settle in India
Customers outside India pay with international cards and other supported methods. The provider converts and settles to your Indian account.
- 01The customer pays in their own currency where that’s supported, or in INR.
- 02Peneu routes it to a provider that accepts that card and business.
- 03You receive the settlement, usually in INR, with the conversion shown on the provider's report.
International Payment Gateway Cross-Border Payments Global payment collection
Unified API and webhooks
One request shape and one event format, whichever provider did the work
Your code talks to Peneu, not to each provider. Statuses, errors and webhooks come back in one format, with the provider's own code kept alongside.
- Request
- Peneu API
- Payment provider
- Payment
- Webhook
// create a payment: the same request, whichever provider handles it create payment amount from your order method UPI reference ORDER-DEMO-2041 idempotency a key you generate once
// the response you get back: one status model across providers payment ORDER-DEMO-2041 status authorized provider Provider B (Provider A timed out) attempts 2 · still one payment
// what the provider sends back: its own format and wording from Provider B status the provider’s own success code reference the provider’s transaction ID // Peneu keeps this as received, then maps it to one status
// the webhook you receive: same format from every provider event payment.authorized payment ORDER-DEMO-2041 provider Provider B raw code kept alongside
payment.createdA payment was requestedpayment.authorizedThe provider approved itpayment.failedIt failed, with the provider's reason keptrefund.processedA refund went throughpayout.processedA payout reached the accountsettlement.batch_closedA settlement batch closed
// later, when the settlement file arrives payment ORDER-DEMO-2041 settlement line found in Provider B’s file status matched // anything that doesn’t match is flagged for review, not guessed
Pseudo-code for illustration, not Peneu's API reference. The API reference comes with sandbox access, provided during onboarding.
Reconciliation
Payments, refunds and settlements matched in one place
Records from every provider are normalised, matched to your references and to the settlements that paid them out. What doesn't match is flagged for review.
TransactionsProvider eventsNormalisedMatchedReconciledILLUSTRATIVE DATA
| Type | Your reference | Provider ref | Amount | Status |
|---|---|---|---|---|
| Payment | ORDER-DEMO-2041 | PA••••81 | ₹2,499.00 | Matched |
| Payment | ORDER-DEMO-2042 | PB••••17 | ₹640.00 | Matched |
| Refund | RF-DEMO-0310 | PB••••55 | ₹640.00 | Matched |
| Settlement | ST-DEMO-0927 | Batch 0927 | ₹2,440.02 | Matched |
| Payment | ORDER-DEMO-2043 | PA••••09 | ₹1,150.00 | To review |
References and amounts are demo data. The settlement line is ORDER-DEMO-2041 less a provider fee and GST on it.
The whole platform
Every Peneu service, around one core
45 services in 7 groups, and the 10 capabilities they share. Each links to its own page.
PENEU45 services · 10 capabilitiesCollect Payments 16 services
Banking & Payouts 8 services
Recharge & Bill Payments 3 services
Verification & KYC 8 services
Lending & Financial Services 3 services
Enterprise Infrastructure 5 services
Global Payments 2 services
Plainly
What orchestration changes, and what it doesn't
Orchestration changes how your systems reach payment providers: one integration instead of several, routing rules instead of hard-coded choices, retries and failover instead of manual switching, and one view of results instead of several dashboards.
It doesn't change who is regulated for what. Collecting and settling money is still done by regulated payment aggregators and banks, under RBI's rules, with your money held by them before settlement. Who contracts with each provider, and how funds flow for your business, is set out during onboarding.
Who it's for, and who it isn't
- Probably not yetOne market, a few methods, and one provider that works well enough.
- Worth a lookTwo or more providers already, or growing volumes you can't afford to lose to an outage.
- Likely to pay offSeveral providers, units or markets, and reconciliation that has become a job in itself.
The full reasoning: do you need payment orchestration?
See payment orchestration on your own flows
Tell us the providers, methods and markets you want to orchestrate, and we'll show you how they'd run on Peneu.