Quick facts
- Price
- $249.00 USD
- ERPNext versions
- —
- Setup time
- 30 min
- License
- One-time perpetual
- Languages
- 11 languages
One-time Purchase
CCAvenue Gateway for ERPNext
A build-to-order CCAvenue integration that ECOSIRE builds, installs, and supports on your ERPNext v15/v16 site. It gives Indian and MENA merchants 200+ payment options, multi-currency settlement, and tokenized recurring billing wired directly into Sales Orders, Sales Invoices, and Payment Entries.
$249.00USD
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Key Features
`CCAvenue Settings` single DocType holding merchant ID, access code and working key as encrypted `Password` fields, plus per-environment (test/live) endpoint toggles
Registers CCAvenue in ERPNext's Payment Gateway framework so it surfaces automatically in `Payment Request`, portal checkout and web forms without per-form patching
AES-256-CBC request encryption of the CCAvenue order payload built inside a `@frappe.whitelist()` server method, never in the browser
Hardened response handler: a second whitelisted endpoint decrypts and validates the callback and rejects tampered or replayed responses before any ledger write
Automatic `Payment Entry` creation/allocation against the originating `Sales Invoice` or `Sales Order`, with CCAvenue tracking ID and payment mode stored on the record
Full 200+ method coverage — net-banking, UPI, cards, wallets, EMI and pay-later — passed through CCAvenue's hosted PCI-DSS page
Multi-currency processing with per-currency settlement account mapping for India and MENA merchants
Smart dynamic routing that selects the acquiring path by currency and card BIN to lift authorization rates
Tokenized recurring billing: stores CCAvenue card tokens against the customer for subscriptions and repeat charges without holding PAN data
`hooks.py` doc events wire payment status transitions to `Payment Request`, invoice status and (optionally) `Subscription` records
Scheduler event (`scheduler_events`) reconciles pending/ambiguous transactions against CCAvenue's order-status API so no payment is left in limbo
Refund and capture actions exposed as guarded whitelisted methods, restricted by a dedicated role profile and permission rules
Client Script hooks on the checkout flow for inline status feedback and redirect handling, degrading gracefully on failure
Structured gateway request/response logging (with secrets redacted) for audit, dispute handling and reconciliation
Built and tested against Frappe/ERPNext v15 and v16, packaged as a clean `bench`-installable app
About this Product
Indian and MENA merchants running ERPNext quickly hit a wall at checkout. ERPNext ships with a short list of built-in payment gateways (Razorpay, PayPal, Stripe, Braintree, PayTM), and CCAvenue — the dominant Indian aggregator carrying net-banking, UPI, EMI, wallets, and multi-currency card processing across 200+ options — is not one of them. Teams end up reconciling CCAvenue settlements by hand, pasting transaction references into Payment Entry, and losing the automatic link between an online payment and the Sales Invoice it settles. There is no native place to hold CCAvenue's working_key and access_code, no handler for its AES-encrypted response callback, and no path to tokenize a card for recurring subscriptions.
Why Choose CCAvenue Gateway for ERPNext
`CCAvenue Settings` single DocType holding merchant ID, access code and working key as encrypted `Password` fields, plus per-environment (test/live) endpoint toggles
Registers CCAvenue in ERPNext's Payment Gateway framework so it surfaces automatically in `Payment Request`, portal checkout and web forms without per-form patching
AES-256-CBC request encryption of the CCAvenue order payload built inside a `@frappe.whitelist()` server method, never in the browser
Hardened response handler: a second whitelisted endpoint decrypts and validates the callback and rejects tampered or replayed responses before any ledger write
Automatic `Payment Entry` creation/allocation against the originating `Sales Invoice` or `Sales Order`, with CCAvenue tracking ID and payment mode stored on the record
Full 200+ method coverage — net-banking, UPI, cards, wallets, EMI and pay-later — passed through CCAvenue's hosted PCI-DSS page
ECOSIRE builds a proper Frappe app — a versioned, bench-installable app with its own module, not a pile of loose customizations — that makes CCAvenue a first-class ERPNext payment integration. We register a CCAvenue Settings single DocType for credentials (merchant ID, access code, working key stored as Password fields), extend ERPNext's Payment Gateway framework so CCAvenue appears anywhere the platform offers online payment (Payment Request, web checkout, the portal), and implement the full request/response cycle. A @frappe.whitelist() server method builds and AES-256-CBC encrypts the order payload, redirects the payer to CCAvenue's PCI-DSS hosted page, and a second whitelisted endpoint decrypts and verifies the callback before it is allowed to touch any ledger.
On a successful, verified response the app creates or updates the linked Payment Entry against the originating Sales Invoice or Sales Order, records the CCAvenue tracking ID and payment mode, and moves the Payment Request to Paid — all through hooks.py doc events and server-side logic rather than manual data entry. Smart dynamic routing chooses the acquiring path per currency and card BIN; tokenized recurring billing stores CCAvenue's card token against a customer for subscription and repeat charges; and a scheduler event (scheduler_events in hooks.py) reconciles pending or ambiguous transactions against CCAvenue's status API so nothing is left stranded in a half-paid state. Role-based permissions and a dedicated role profile keep the working key and refund actions off-limits to ordinary users, and every gateway call is logged for audit.
Because this is build-to-order, nothing is a blind download. We start with a scoping call to confirm your ERPNext version (v15 or v16), currencies, settlement accounts, and whether you need recurring billing or one-time checkout. ECOSIRE then builds the app to your scope, proves it on a staging site through UAT, and installs it on production with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope. You receive the full source, a git repository handover, technical and user documentation, a training session, and a post-go-live support window.
What you get
- Installable source code for your build — a versioned, `bench get-app` / `bench install-app` ready Frappe app scoped to your ERPNext version
- Installation and configuration on your environment, including `CCAvenue Settings` credential setup and settlement-account mapping
- Technical documentation: DocType schema, hooks.py doc events, whitelisted methods, scheduler jobs, and the encryption/callback flow
- User guide plus a live training session for finance and operations staff covering checkout, reconciliation and refunds
- UAT on a staging site with test-mode CCAvenue credentials, plus a documented rollback plan before production cutover
- Post-go-live support window for defect fixes and configuration help after launch
- Git repository handover with full commit history so your team owns and can extend the code
- Handover checklist covering permissions/role profile, scheduler enablement, and live-credential switchover
Who this is for
Indian D2C / retail merchant on ERPNext
Sells across UPI, net-banking, cards and EMI and needs every CCAvenue method live at checkout, with each online payment auto-reconciled to its Sales Invoice instead of manual Payment Entry work.
MENA multi-currency seller
Bills customers in INR, AED, SAR and USD and needs per-currency settlement mapping plus smart routing to keep authorization rates high across regions CCAvenue serves.
Subscription / recurring-revenue business
Runs memberships or repeat billing and needs CCAvenue card tokenization tied to ERPNext Subscriptions so renewals charge automatically without storing card data in-house.
ERPNext implementation partner or in-house admin
Wants a clean, documented, upgrade-safe app with a git handover and role-based permissions — not brittle customizations — so the gateway survives v15-to-v16 upgrades and audits.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the CCAvenue Gateway for ERPNext app ZIP from your account dashboard.
Add the app to your bench
Extract the ZIP into your bench's apps folder, or run `bench get-app` with the path to the extracted app.
Install on your site
Run `bench --site SITE_NAME install-app APP_NAME` followed by `bench migrate` to install CCAvenue Gateway for ERPNext and apply its schema.
Activate your license
Open the ECOSIRE License settings on your site and activate your license key. Requires the free ecosire_connect and ecosire_license_client apps.
How CCAvenue Gateway for ERPNext Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| CCAvenue availability in ERPNext | First-class integration in the Payment Gateway framework | Possible but you scope and build it yourself | May exist but often unmaintained across versions | |
| Method coverage | All 200+ CCAvenue options (UPI, net-banking, cards, EMI, wallets) | Whatever you have time to implement | Core methods, EMI/wallets often missing | |
| Invoice reconciliation | Auto Payment Entry against Sales Invoice/Order via doc events | Manual unless you build the linkage | Basic; edge cases often left manual | |
| Recurring / tokenized billing | CCAvenue tokenization tied to ERPNext Subscriptions | Significant extra build effort | Rarely supported | |
| Multi-currency & smart routing | Per-currency settlement mapping + BIN-based routing | You design and test the routing logic | Single-currency assumptions common | |
| Security of credentials & callback | Encrypted Password fields + server-side AES verify + role profile | Depends entirely on your implementation | Varies; verification sometimes weak | |
| v15/v16 upgrade safety | Clean bench app, tested on both, git handover | Maintenance burden falls on you | Upgrade lag and abandonment risk | |
| Support & ownership | Post-go-live window, docs, training, full source | Self-supported | Vendor-dependent, variable SLAs |
Frequently Asked Questions about CCAvenue Gateway for ERPNext
+Is this a ready-made app I can download and install today?
No. It is build-to-order. ECOSIRE builds, installs and supports the CCAvenue integration for your specific ERPNext site after we confirm scope on a call. There is no instant download — we deliver working, tested source built to your version and requirements.
+How long does delivery take?
Typical delivery is 2–4 weeks from confirmed scope. The timeline depends on your ERPNext version, the currencies and settlement accounts involved, and whether you need one-time checkout only or tokenized recurring billing. We agree the exact timeline in the scoping call before any build starts.
+Which ERPNext versions are supported?
We build and test against Frappe/ERPNext v15 and v16, packaged as a clean bench-installable app. Confirm your running version on the scoping call and we target that; if you plan to upgrade, we account for it in the build.
+How do you handle support and updates after go-live?
Every build includes a post-go-live support window for defect fixes and configuration help. Because you receive the full source and git repository, your team can extend the app; ECOSIRE also offers ongoing maintenance and version-upgrade work as a separate engagement if you prefer we keep it current.
+Is it secure — where do card details and the working key live?
Card entry happens on CCAvenue's PCI-DSS hosted page, so your ERPNext site never stores raw card data. The working key and access code are held as encrypted Password fields in CCAvenue Settings, the AES-encrypted callback is verified server-side before any ledger write, and refund/credential actions are restricted by a dedicated role profile.
+Does a payment automatically reconcile to the invoice?
Yes. On a verified successful response the app creates or allocates a Payment Entry against the originating Sales Invoice or Sales Order, records the CCAvenue tracking ID, and updates the Payment Request status — driven by hooks.py doc events, with a scheduler job that reconciles any pending transactions against CCAvenue's status API.
+Can it handle subscriptions and recurring charges?
Yes, when in scope. We implement CCAvenue card tokenization stored against the customer and wire it to ERPNext Subscriptions so renewals charge automatically without holding PAN data on your servers. Tell us on the call whether recurring billing is required so we build it in.
Request a quote
CCAvenue Gateway for ERPNext
A build-to-order CCAvenue integration that ECOSIRE builds, installs, and supports on your ERPNext v15/v16 site. It gives Indian and MENA merchants 200+ payment options, multi-currency settlement, and tokenized recurring billing wired directly into Sales Orders, Sales Invoices, and Payment Entries.
- `CCAvenue Settings` single DocType holding merchant ID, access code and working key as encrypted `Password` fields, plus per-environment (test/live) endpoint toggles
- Registers CCAvenue in ERPNext's Payment Gateway framework so it surfaces automatically in `Payment Request`, portal checkout and web forms without per-form patching
- AES-256-CBC request encryption of the CCAvenue order payload built inside a `@frappe.whitelist()` server method, never in the browser
- Hardened response handler: a second whitelisted endpoint decrypts and validates the callback and rejects tampered or replayed responses before any ledger write