Cashfree is a sensible fit for Indian businesses that need UPI-first collections, Autopay subscriptions and vendor payouts in one account. Most of the work is server-side: orders, signatures, webhooks and a ledger that survives a failed payment.
UPI · Cards · Netbanking · Autopay · Payouts · GST invoices
Cashfree checkout covers UPI intent and collect, cards, netbanking, wallets and EMI. The Flutter app should never decide the amount: the backend creates the order with an amount, receipt and customer id, then hands the app a payment session or token.
UPI has more pending states than cards. The UI needs a clear 'waiting for confirmation' state and a way back to the order, not a spinner that ends in a dead screen.
Cashfree returns a signature with the payment. Verify it on your server before anything is marked paid, and treat webhooks as the source of truth for captured, failed and user-dropped payments.
Handlers need to be idempotent: gateways retry webhooks, and the same event arriving twice should never create two orders or extend a subscription twice.
Recurring payments use UPI Autopay, card mandates or eNACH depending on the amount and the customer's bank. The backend creates the plan and subscription, stores the mandate id, and listens for debit, failure, halt and cancellation events.
Access is granted from the server-side entitlement, with grace periods for failed retries. The app only mirrors that state.
Marketplaces and platforms also need money out. Cashfree Payouts can pay vendors, sellers or delivery partners after beneficiary verification, with transfer status delivered by webhook.
Refunds, settlement reports and GST invoice details should reconcile against your own payment table so finance can close the month without manual exports.
Explore examples of mobile, Smart TV and integrated product work.
Both are established Indian payment gateways. The decision usually comes down to your pricing and settlement terms, payout requirements, subscription features and support. I integrate whichever account your business already holds, and I will flag it if the choice is creating unnecessary complexity.
Yes, through UPI Autopay and card mandates. Plans and subscriptions are created on the server; the app handles authorisation. Renewals and failures arrive as webhook events, so access should be granted from your backend.
Usually. Existing mandates often cannot be moved, so those customers may need to re-authorise. One-time payment history can be retained. I run both providers during the transition and keep the old webhook alive until reconciliation is clean.
A standard one-time payment flow is a few days including test payments. Autopay, payouts and reconciliation take longer because they touch billing records, bank details and finance reporting.
