Skip to main content
CashFree Wallets is a wallet payment method in India. Customers pay from the balance of a supported mobile wallet and confirm each payment with their wallet provider. Payrails processes CashFree Wallets through two payment service providers (PSPs). The flow is the same with each one, but the required request fields differ. Pick a PSP below for its setup steps and request examples.

​
How a CashFree Wallets payment works

CashFree Wallets is a redirect payment method:
  1. The customer selects CashFree Wallets at checkout.
  2. Payrails returns a redirect URL from the PSP, and the customer goes to the PSP’s payment page.
  3. The customer chooses their wallet, signs in, and confirms the payment.
  4. The customer returns to your returnInfo URL.
  5. Payrails receives the final result from the PSP and updates the payment.
Each payment is single-use: the customer confirms every payment on its own. Payrails captures CashFree Wallets payments immediately, so a successful payment is final. To return funds, refund the payment.

​
Supported currencies and countries

CashFree Wallets supports INR (Indian rupee) as its only presentment currency.

​
Integrate CashFree Wallets

Choose the PSP that processes CashFree Wallets for you. Each guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

dLocal

CashFree Wallets via dLocal

Pine Labs

CashFree Wallets via Pine Labs

​
Compare PSPs

Neither PSP stores a reusable wallet token, so Save Instruments and merchant-initiated transactions (MIT) aren’t available for CashFree Wallets.

​
Ways to integrate CashFree Wallets

  • Payrails SDK: the Web SDK shows CashFree Wallets when your workflow returns it as a payment option, and redirects the customer to the PSP. To control how the redirect opens, listen for the actionRequired event.
  • Payrails API: call lookup payment options, then authorize with cashFreeWallet as the paymentMethodCode. Each PSP guide lists the meta fields that PSP requires.
In both cases, confirm the final result through webhook notifications or the execution status. Don’t treat the customer’s return to your success URL as proof of payment.
Last modified on October 2, 2026