Fintech APIs & Platform for KYC, Verification & Transactions in India | Eko Platform Services
Eko Platform Services Logo
← Back to Home

Prepaid Payment Instrument (PPI) Wallet API

Let retailers and agents open prepaid wallets for customers, complete Aadhaar (incl. multilingual e-KYC consent) and PAN KYC, load funds, and transfer money from the wallet to any bank account using IMPS and NEFT — with real-time status and receipts.

Get Sandbox Access View Documentation
Prepaid Payment Instrument (PPI) Wallet API

Key Features

Everything you need to integrate and scale

Assisted Wallet Onboarding

Open a customer's PPI wallet in seconds with OTP-based sender onboarding.

Aadhaar & PAN KYC

Upgrade wallet limits with Aadhaar OTP and PAN validation, fully API-driven.

Wallet-to-Bank Transfers

Move funds from the wallet to any bank account via IMPS and NEFT.

Recipient Management

Add and reuse beneficiaries with bank-account verification.

Real-time Status

Transaction inquiry and OTP-secured flows with audit trails.

Why Choose Eko?

Higher Wallet Limits

Tiered monthly limits unlocked through Aadhaar and PAN KYC.

Earn Commission

Earn on every successful wallet transfer processed through your network.

Regulatory Compliant

Built for RBI PPI workflows with KYC, consent, and transaction controls.

Primary Use Cases

Assisted Banking Networks
Kirana Stores
Agent Banking
CSP/BC networks
Retail Wallet Apps

How to Integrate

Get started in minutes with our simple integration process

  1. 1

    Sign Up

    Sign up in minutes with your mobile number (OTP verify).

  2. 2

    Verify Identity

    Provide your PAN and bank account details to verify your account.

  3. 3

    Test APIs Live

    Load funds into your wallet and test the verification APIs live — evaluate before you integrate.

  4. 4

    Integrate with AI

    Ready to build? Visit our AI hub for free plugins & tools to integrate faster.

  5. 5

    Go Live

    Get production credentials and start opening wallets and processing transfers.

Frequently Asked Questions

What KYC is needed to raise wallet limits?+

Sender onboarding uses OTP; limits are upgraded with Aadhaar OTP validation and PAN verification, all via API.

How does money leave the wallet?+

Add a recipient bank account, send a transaction OTP, then initiate the transfer — funds move via IMPS (instant) or NEFT.

How do I get started?+

Sign up at ekostore.app/eps, verify your identity (PAN + bank account), load your wallet to test the verification APIs live, then integrate and go live.

What are the different ways to integrate with Eko?+

Integrate in whichever way suits your stack: call the REST APIs directly, use our official SDKs (JavaScript and PHP) to skip request-signing boilerplate, or let an AI coding agent build the integration using our MCP server and skills. See the Developers and AI sections for each path.

How does API authentication work?+

Each request carries your static `developer_key` header plus a per-request `secret-key` header — an HMAC-SHA256 signature of the current timestamp, keyed by your access key. The access key itself is never sent over the wire. You receive UAT keys on signup and production keys after KYC.

Is there a sandbox environment for testing?+

Yes. A full sandbox environment is available immediately on signup. You can test your integration end-to-end before going live — no commitment required.

Also see:Get started
What are the sandbox and production base URLs?+

Sandbox and production share the same paths and differ only by base URL: use https://staging.eko.in/ekoapi/v3 for UAT / Sandbox, and https://api.eko.in/ekoicici/v3 for Production. A common cause of failures is calling the sandbox/staging URL with live credentials (or vice-versa) — make sure the base URL matches the keys you are using.

Do I need to whitelist my server IP?+

Production API access may require your static public (server) IP to be whitelisted. If your calls work from Postman but fail or time out from your own server, share your static public IP with us so we can whitelist it.

What response times can I expect?+

Most verification APIs return in real time with sub-second responses, and 99th-percentile latency stays under two seconds across verification endpoints. Transaction APIs (DMT, AePS, BBPS) respond within seconds.

Can the API handle high volumes?+

Yes. The API is designed to handle large-scale volumes reliably without performance degradation.

How is API usage billed?+

Usage is billed per successful API call with no minimum commitment. Volume-based pricing tiers are available — contact our team for detailed rates.

Get API Access

Sign up now and start integrating in minutes. Our team will help you go live quickly.

  • Sandbox access in minutes
  • Dedicated integration support
  • Comprehensive documentation
  • Reliable, high-volume workflows

Get API Access

Get started in 10 minutes