Partner with Peneu

Who this is for

Partners are the institutions whose services businesses reach through Peneu. Each keeps its own regulatory position; the orchestration layer changes how businesses reach a service, not who is responsible for it.

Banks: Acquiring, settlement and account banks offering collections, payouts, virtual accounts or API banking to businesses.
PSPs: Payment aggregators and gateways whose acceptance methods can sit behind an orchestration layer as one of a business's routes.
TSPs: Technology service providers for processing, tokenisation, checkout or verification that payment flows depend on.
NBFCs: Lenders offering working capital, credit lines or other credit to businesses, within RBI's rules for digital lending.
Financial infrastructure providers: Bill-payment, payout, cross-border, KYC and other specialist providers, plus institutions such as prepaid-instrument and card issuers.

Integration and distribution partnerships

Integration

Your service becomes one of the routes or components inside the orchestration layer: connectivity, status and reconciliation data, and how incidents are handled on both sides. Where it applies, integration work is built and tested in a sandbox before anything reaches production.

Distribution

Businesses using Peneu can be introduced to your products where they fit. Who holds the customer relationship and how it's paid for are agreed commercially; nothing is promised in advance about volume.

Referral and other commercially agreed models are possible too; say what you have in mind in the enquiry.

What stays with the regulated partner

Connecting behind an orchestration layer doesn't move a regulated entity's obligations. Customer due diligence, how funds move and are held, and reporting to the regulator stay with the bank, payment aggregator, lender or issuer whose service it is.

The rules depend on the service. Payment aggregators work under RBI's Master Direction on payment aggregators, and credit offered digitally falls under the Digital Lending Directions, 2025. The RBI rules reference lists the directions cited across this site; it's a summary, not legal advice.

After you send it

The enquiry reaches the team, marked as a partnership enquiry, and a reply comes by email.
If there's a fit, a first call covers your services, the businesses they suit and the partnership model.
Technical, commercial and compliance detail follows only if both sides want to continue.

The full journey, from review to go-live, is on the contact page. See also the partners page.

Questions partners ask

Does sending an enquiry make us a Peneu partner?

No. An enquiry starts a conversation. Any partnership depends on a review on both sides, a commercial agreement and whatever approvals apply to the services involved.

Which documents do we need to start?

None for the enquiry. Licensing, compliance and security documents are requested later, if the conversation moves forward and only for what the partnership needs.

Does Peneu guarantee merchant volume or revenue?

No. Distribution, volumes and commercial terms are agreed case by case, and nothing on this site promises merchant numbers, transaction volume or revenue.

Can we enquire if we don't have an API yet?

Yes. Say how your service is delivered today and what's planned. Integration options are part of the discovery conversation, and some partnerships, such as referral arrangements, may not need one.

Are the partner categories on the contact page live integrations?

No. They describe the kinds of institution an orchestration layer can connect, not integrations that are live. Named connections are listed on the partners page only once they're live and verified.

Where does the enquiry go?

It's sent to Peneu through the same enquiry system as the contact form, marked as a partnership enquiry. You can also write to the partnerships address shown on this page.