Hosted checkout & auto-charge — what is and isn't live

The payment-gateway interface and an encrypted credential vault are built, and the auto-charge mandate schema is designed (its migration is deferred); no gateway is wired in yet, so hosted checkout links and auto-charge are not live, and Finocket never moves money itself. UPI pay-now already collects in the customer's own app. Here's where that stands.

Finocket already lets your customer pay an invoice — every open invoice on the client portal and the invoice PDF carries a UPI intent link and QR for the exact outstanding, so they scan or tap and pay in their own UPI app. A hosted gateway checkout (a pay page the gateway hosts) and auto-charge mandates (recurring authorisations) need a payment gateway wired in the middle.

What is live today

The plumbing for a gateway is built and secure — but no gateway is wired in yet, so nothing charges on its own. Concretely:

Built: the gateway interface (verify credentials, create a hosted checkout link, create/cancel a mandate, charge an active mandate, verify a webhook) and an encrypted credential vault (AES-256-GCM) to hold a gateway account's secrets safely.
Designed, not migrated: the mandate record shape (which client, which gateway, the per-charge ceiling, the cadence, the expiry) is designed, but its database table is deliberately not created until a gateway is chosen — so there is no unused table sitting in production.
Not live: hosted checkout links and auto-charge. No gateway is available to select yet, so the connect form on Settings → Payment gateway shows the honest “no payment gateway connected” state. Auto-charge switches on only once a gateway is chosen and its credentials are connected.

Finocket never moves money itself

This is a hard rule. Finocket does not hold funds, does not take card details, and does not run charges. When a gateway is wired, the gateway hosts the payment page and executes every charge; Finocket only creates the link, records the outcome and reconciles it. A mandate can be charged only when the customer has approved it and only up to the ceiling they authorised — never more.

Why a gateway is required

Executing a card or account charge is a regulated activity that flows through a licensed payment gateway. Choosing one is a commercial decision (pricing, settlement, mandate support), so Finocket ships the vendor-neutral interface and vault now and lets you connect the gateway you pick, without a product update.

What you can do in the meantime

Share the invoice — the client portal and the PDF already carry a UPI intent link and QR for the exact balance, so your customer pays in their own UPI app.
Record the payment on Add → Payment when it lands, and it flows into your books and receivables as usual.

Claims discipline: the payment-gateway interface and the credential vault are built; the mandate schema is designed but its migration is deferred; no gateway is connected yet, so Finocket does not create hosted checkout links or auto-charge today, and never moves money itself. UPI pay-now does the collection job in the customer's own app. We will say so plainly until a gateway is live.

Frequently asked questions

Can Finocket auto-charge my customers?

Not yet. The payment-gateway interface and a secure credential vault are built, and the mandate record is designed, but no gateway is connected and the mandate table is not migrated, so hosted checkout links and auto-charge are not live. UPI pay-now (a UPI intent link + QR on the portal and PDF) collects in the customer's own app in the meantime.

Does Finocket ever move money itself?

No — never. Finocket holds no funds, takes no card details and runs no charges. When a gateway is wired, the gateway hosts the payment page and executes every charge; Finocket only creates the link, records the outcome and reconciles it. A mandate can be charged only after the customer approves it, and only up to the ceiling they authorised.

Are my gateway credentials safe if I connect them?

Yes. Credentials are encrypted with AES-256-GCM before they ever reach the database, are bound to your company so a copied row can't be decrypted elsewhere, are never shown again after saving, and only the company owner can manage them.

What can I do until auto-charge is ready?

Share the invoice — the client portal and the PDF already carry a UPI intent link and QR for the exact balance, so your customer pays in their own UPI app — and record the payment on Add → Payment when it lands. It flows into your books and receivables as usual.

Clients, projects and invoices

Add clients with GSTIN + state auto-fill. Send invoices — tax invoice, bill of supply, export invoice, receipt or credit note — start from an estimate, or split an invoice into a deposit + milestone schedule.

Estimates, deposits and payment schedules

Send an EST-numbered estimate with a hosted accept link — your client accepts with a typed name recorded with a timestamp — convert it to an invoice in one tap, and collect through a deposit or milestone schedule that chases itself.

Progress billing and invoice templates

Bill an estimate, sales order or retainer in tranches — by percentage or amount — with a running billed/remaining tally that can never over-bill the job to the paisa, and pick from three invoice PDF templates that each keep your show-on-PDF custom fields.