CCAvenue
Takes payments online through the workspace's own CCAvenue account. Customers pay invoices, shop orders, event tickets and course places by UPI, card, netbanking or wallet on CCAvenue's secure page, the money settles straight into your account, and refunds go back the same way.
| At a glance | |
|---|---|
| Type | Add-on module |
| Group | Bill |
| Price | Free (CCAvenue charges its own fees on your account) |
| Provides | Take payments online, Generate payment links |
| Needs | The Payments module, and a workspace in rupees |
| Offered to | Every industry pack |
| Permission | Manage add-ons (addons.manage) to switch it on; Manage settings to connect the account |
What it does
CCAvenue is a payment gateway add-on module of Payments. While it is on and connected, Payments can:
- take payment online on an invoice's pay page (the shared receipt link and the customer portal), at the online shop's checkout, for event tickets, for course places and at the self-order kiosk. Pay now passes through a short Taking you to CCAvenue page that sends the payment, encrypted with your working key, to CCAvenue's own page; the customer pays there and CCAvenue brings them back;
- let staff Collect online on an invoice, with a page to send the customer;
- send money back through CCAvenue when a payment is refunded;
- make pay-now links, sent by text or WhatsApp (they need an SMS or WhatsApp add-on module as well).
CCAvenue cannot pay Subscriptions renewal bills automatically: it publishes no way to charge a saved card, so a workspace taking payments through CCAvenue sees automatic payment as not available. Customers pay those bills as ordinary bills.
Every payment is checked with CCAvenue's own status service before it is recorded: what the customer's browser brings back is never enough on its own.
Currencies. Rupees only.
Switching it on
- Switch on Payments first (Workspace → Modules). CCAvenue needs it, so the switch is refused while Payments is off.
- Set the filter to Add-on modules. CCAvenue is under Bill.
- Open its ⋮ menu, choose Enable, and press Enable in the dialog. There is nothing to fill in there.
- Choose Connect under Settings → Payments on its ⋮ menu and connect your account (below).
Connecting your CCAvenue account
Settings → Payments, provider CCAvenue:
| Field | What to enter |
|---|---|
| Merchant ID | CCAvenue dashboard → Settings → API Keys (a number). |
| Access code | The access code for the website you take payments on. |
| Working key | The working key (the encryption key). Write-only. |
| Environment | Test (no real money) or Live. |
| Accept payments through this gateway | Tick it to take payments. Needs all three. |
Before you go live:
- Register the server's address with CCAvenue. CCAvenue answers its status service only from server addresses registered in your CCAvenue account. Ask platform support for them and register them, or payments cannot be confirmed.
- Register your website address with CCAvenue if your account asks for it (the address your customers pay from).
No webhook. CCAvenue does not publish one. A payment is recorded when the customer comes back from CCAvenue, and any payment still open is checked with CCAvenue again every ten minutes for three days.
Refunds go back through CCAvenue; one reads refunded once CCAvenue's status for the order says so.
One gateway takes payments at a time. To move to another, switch this one's Accept payments off first.
Turning it off
Turn off on the ⋮ menu asks first. New online payments through CCAvenue stop at once, and CCAvenue leaves Settings → Payments. Payments already under way are still recorded when CCAvenue confirms them, refunds of earlier payments still go back through it, and the keys stay saved for when it is switched on again. While CCAvenue is on, Payments cannot be switched off.
Ready-made automations
None of its own. The moments around a payment (one that fails, a pay-now link to send) are the Payments module's ready-made automations.
In the desktop and mobile apps
Not carried. The apps take payment at the counter.