Company · why Peneu
Do you need payment orchestration? An honest answer.
Peneu is a payment orchestration platform: one integration in front of multiple payment providers, with routing, retries, failover and reconciliation. That's valuable for some businesses and unnecessary for others. This page helps you tell which you are.
You probably don't need it yet
One market, a few methods, one provider that works.
It's worth a look
Two or more providers, or growing volumes you can't afford to drop.
It's likely to pay off
Several providers, units or markets, and outages that cost real money.
What orchestration actually does
Without orchestration, every payment provider is its own integration: its own API, its own webhooks, its own reports and its own dashboard. Add a second provider for resilience or coverage and the work doubles, and so does reconciliation.
An orchestration layer puts one integration in front of them. Your systems talk to it; it talks to the providers. Rules you set decide which provider handles each payment, what happens when one fails, and how results come back to you. See the platform for how Peneu describes each capability.
One integration. One API and one webhook model in front of the providers you connect.
Routing. Rules decide which provider handles which payments.
Retry and failover. Recoverable failures retried; traffic moved when a provider degrades.
One view. Transactions, settlements and reconciliation across providers.
Three ways to set up payments
Each approach suits different businesses. The comparison below is about the approaches, not about any particular bank or provider.
| Direct bank integration | Single payment provider | Orchestration layer | |
|---|---|---|---|
| Integrations to build | One per bank and product | One | One, to the layer |
| Payment methods | What that bank offers | What that provider offers | What the connected providers offer together |
| If the provider has an outage | Payments stop on that path | Payments stop | Traffic can move to another provider |
| Reconciliation | Bank statements | One provider's reports | Combined across providers |
| Negotiating position | Per bank | Tied to one provider | Spread across providers |
| Added complexity | Bank-specific work | Lowest | A layer to understand and configure |
Real setups often mix these: for example, a direct bank integration for payouts and orchestration for collections.
When one provider is enough
If you sell in one market, need a handful of payment methods, and your provider's reliability and pricing are acceptable, adding a layer adds cost and complexity for little gain. Spend the effort on checkout, reconciliation and refunds instead.
Keep the door open by not building deep, provider-specific assumptions into your own systems, so moving later isn't a rebuild.
Signs you're fine as you are
- An outage would be an inconvenience, not a crisis
- Your methods and markets are all covered
- Month-end reconciliation takes hours, not days
- You have no second provider to manage
When orchestration pays off
Downtime is expensive
Minutes of failed payments on a sale day cost more than a second integration.
You already run several providers
And your team maintains each integration separately.
Coverage gaps
One provider is strong in cards, another in UPI or international payments.
Reconciliation hurts
Reports in several formats, matched by hand.
Questions to ask any orchestration platform, including us
- 01Which payment providers and methods can you connect for my business, today?
- 02How are routing decisions made, and can I see why a payment went where it did?
- 03Who contracts with the payment providers, and where does my money sit?
- 04What happens to in-flight payments during a provider outage?
- 05How does reconciliation work across providers, and in what formats?
- 06What does it cost, including every provider's own charges?
For Peneu, the answers depend on your business and are set out during onboarding. Pricing plans are on the pricing page.
What you won't find on this site
No customer logos, success-rate percentages, transaction volumes or certification badges. Not because they don't matter, but because Peneu only publishes them once they're verified, and asks you to check them during due diligence rather than take a website's word for it.
The guides across this site explain how payments work in India, with sources for the rules they quote. We'd rather you understood the subject than were impressed by a number.
Orchestration questions
What is payment orchestration?
A layer between your systems and several payment providers. You integrate once; the layer sends each payment to a provider under rules you set, retries or fails over when a provider has a problem, and brings every provider's results and reports into one view.
Is orchestration the same as a payment aggregator?
No. A payment aggregator is a regulated business that collects payments for merchants and settles them. An orchestration layer sits in front of one or more such providers and decides how payments flow between them.
Do small businesses need orchestration?
Often not at first. A business with one market, a few payment methods and modest volume is usually well served by one good provider. Orchestration starts paying off with several providers, higher volumes, or when an outage costs real money.
Who holds the money when orchestration is used?
The regulated banks and payment providers that process the payments. Who contracts with them and how funds flow depends on the setup; for Peneu, it's set out during onboarding.
Why doesn't this page show customer numbers or success rates?
Because Peneu publishes figures, customer names and certifications only once they're verified. Claims you can't check aren't a good basis for choosing a payments partner.