CCAvenue Integration -WooCommerce | Notion

CCAvenue provides three main integrations in their JDK build.

Summary Table

Feature	Non-Seamless	Iframe	Custom Data
Where payment UI loads	CCAvenue page (redirect)	Inside your site in iframe	N/A
Who styles payment form	CCAvenue only	CCAvenue (in iframe)	N/A
Extra merchant fields	Possible	Possible	Yes, main purpose
PCI scope	Lower	Lower (same as non-seamless)	N/A
User stays on site	No	Yes	N/A

1. Non-Seamless Integration

File Structure

1.1 Concept

Your Site → Backend (encrypted) → Redirect to CCAvenue’s payment page.

1.2 Flow

Customer fills a form on your site (amount, name, etc.).
Form is submitted to your backend.
Backend encrypts the data using your Working Key.
Backend responds with an HTML form that auto-submits to CCAvenue’s payment URL.
User is taken to CCAvenue-hosted payment page (full redirect).

1.3 Adv & Disadv

Pros

Cons

Very easy to implement.
Working Key stays server-side.
PCI DSS compliance burden is lower.
User leaves your website (full page redirect).
Payment UI is fully CCAvenue’s — limited control over styling.

1.4 Code