CCAvenue is an auto-settle payment method offering locale India payment options such as Credit Card, Wallet, Net Banking, and UPI.
Configuring CCAvenue for DigitalRiver.js
Create a method for your app or website in four easy steps:
Step 1: Build a CCAvenue Source Request and Details object
Build the CCAvenue Source Request and Details objects.
CCAvenue Source Request object
The CCAvenue Source Request object requires the following fields.
CCAvenue Source Details object
The CCAvenue Source Details object requires the following fields.
The CCAvenue Source Details object requires the following field.
Step 2: Create a CCAvenue source using DigitalRiver.js
Use the DigitalRiver.js library to create and mount elements to the HTML container.
CCAvenue source example
Payment options
CCAvenue offers multiple payment options. The bankCode identifies the payment options and determines the value of the subType field.
The bankCode value will be used as the subType unless the bankCode is "Credit Card", then the bankName will be used as the subType.
Step 3: Authorize the CCAvenue source
When you create a CCAvenue source, the customer must authorize the charge through their payment provider. You can accomplish this by redirecting the customer to their payment provider.
Redirecting the customer for CCAvenue authorization
Use the redirectUrl parameter in your createSource response to redirect your customer to the payment provider for authorization.
The payment provider will present the customer with the transaction details, and the customer can authorize or cancel the transaction. A successful authorization redirects the customer to the CCAvenue Return URL parameter specified when you created the source.
Once authorized, the source state will change to chargeable.
Step 4: Use the authorized source
Once authorized, you can use the source by attaching it to a cart or a customer.
Option 1: Attach the source to the cart
Option 2: Attach the source to a customer
Testing CCAvenue
You can test your payment integration in the CCAvenue sandbox. When evaluating your integration, always use your test API keys. This prevents you from interacting directly with payment services and ensures that the test data you enter does not create an actual charge or result in the transfer of funds.
Use your confidential (secret) test API key when conducting testing in the Digital River API. Use your public test API key to create test payment sources in DigitalRiver.js.
Your testing approach depends on whether the payment method has an authentication flow of redirect. If you don't know the flow of the payment method you'd like to test, you can find it on the Supported payment methods page.
Use the following payment information when running a test.
Supported markets
For information on supported markets and currencies for Drop-in and DigitalRiver.js, go to: