Payments — collect from your customers with payment links

Create payment links from invoices, collect by UPI, card, netbanking or wallet through your Razorpay account, and get a payment record when it settles.

Part of AxisIQ's single business model — The financial record (Know the business). How the layers fit.

Getting paid is often the least automated step in a business that has automated everything else: the invoice goes out on WhatsApp, the customer pays by UPI to a number somebody shared last year, and a week later someone is matching a bank statement against a spreadsheet, guessing which credit belongs to which order. AxisIQ Payments closes that gap — you create a hosted payment link, your customer pays it by UPI, card, netbanking or wallet through your own payment provider account, and the settled payment lands in your workspace as a record attached to the invoice it paid.

Payments is you charging your customers, through your own provider account. Money moves from your customer to your provider and settles to your bank exactly as it does today. AxisIQ never sits in the flow of funds — it creates the link, listens for the outcome, and writes down what happened.

Connect your provider once

A connection is your provider account, held in AxisIQ so links can be created against it. Razorpay is the provider today, which covers UPI, cards, netbanking and wallets for a business collecting in India. Three things are true of the keys you paste.

  • They are sealed with AES-256-GCM encryption before they are stored, and the sealed value is never handed back out.
  • You see them once. Nothing shows them again afterwards — not to you, not to the owner.
  • Every save is proved against the provider before it is kept. If the provider rejects what you entered, nothing changes and the connection you had carries on. Renaming a connection or changing its return address never means re-pasting a secret.

You can test a saved connection whenever you like — the quickest way to find out that a key was rotated on the provider's side.

A manual link is an amount and a description — what you want when someone owes you for a deposit, a one-off, or something not yet invoiced.

An invoice-bound link starts from a record you already have. Pick the invoice and the amount and customer details fill in from it, read under your own permissions, so a link never surfaces a field you were not allowed to see. The payment that eventually arrives points back at that invoice.

Either way the customer gets a hosted page in their browser, with UPI, cards, netbanking and wallets offered as your provider account allows.

To deliver it, paste it into whatever channel you already use with that customer, or send it from AxisIQ by email, SMS or WhatsApp through a provider account your company connects in Phone & Messages — by hand, from a flow, or by asking Axis.

Settlement nobody has to watch

When the link is paid, your provider notifies AxisIQ and a payment record appears in your workspace carrying the amount, the method used and the provider's own payment id.

Exactly once. The provider's payment id becomes the payment record's number, and that number has to be unique. A notification delivered twice — as providers do deliberately when they cannot be sure the first arrived — finds the record already there and changes nothing. No duplicate payments, and no reconciling your reconciliation.

Recoverable. Notifications do sometimes go missing — a network blip, an outage, a restart at the wrong second. Every link has a Refresh action that asks the provider for its current state and settles it on the spot. One click, not a support ticket.

The invoice does not close itself

The payment record links to the invoice it paid. The invoice's own status stays exactly where it was until a person moves it.

That is a decision, not a missing feature. Part payments, overpayments, advances and money that lands against the wrong invoice are all ordinary events, and software that quietly marks things paid is how a receivables list stops being believable. AxisIQ records the fact and leaves the judgement to you.

If your business really has no ambiguity — one link, one invoice, paid in full or not at all — automate it yourself. A flow triggered on payment record created can set the invoice status or start fulfilment. See Automation.

Reminders that chase for you

Unpaid invoices get a reminder on the days you choose — a few days before the due date, on the day, then a week and a fortnight late — sent from your own email or SMS account with a link to pay. They stop the moment the invoice is paid or cancelled, each one goes out once, and switching them on never dumps a backlog of old reminders on your customers. One invoice can be paused when a customer has asked for more time.

A statement when the customer asks

Pick a customer and a period and you get their statement of account: opening balance, every invoice, payment, credit note and TDS deduction with a running balance, and what is still unpaid by age. Download it as a PDF with your name and logo and send it on.

Where the customer lands afterwards

Every link works out a return address in order: the one set on that link, then the default on the connection, then a hosted receipt page that says plainly whether the payment went through. A customer paying from your website returns to your website; one paying a link you sent by hand still lands somewhere sensible, with nothing to configure.

Collecting money and holding the keys are different jobs, so they are different permissions: one to see that a connection exists, one to create and edit connections and their credentials, one to raise links against them.

A collections assistant can send links all day with no route to your provider keys; someone in finance can manage the connection without raising a single link. These are ordinary rules in Team & Permissions, not a separate admin corner with its own logic.

Why not just use your provider's own dashboard

Honestly: if all you need is to send someone a link, your provider already does that, and you should use it.

What a payment dashboard cannot know is what the money was for. It holds the transaction — not your invoice, your order, the customer record, or the packing step that should start when payment clears — and reconciliation is the work of joining those up by hand, days later.

Payments inside AxisIQ earns its place when the link begins at a record and the settlement returns to one: the link knows the invoice, the payment sits beside the order, and reports count collections with nothing exported.

What is not in it

  • One provider. Razorpay, and only Razorpay today. A second provider would be an addition to the same connection model rather than a redesign, but one is what exists.
  • No recurring collection. Subscriptions, mandates and auto-debit are not built — each link is a single payment.
  • No sender of its own. AxisIQ sends links only through an email, SMS or WhatsApp provider account your company connects.
  • Ledger posting is per document type. A settled payment posts to the ledger only when it settles an invoice of a document type with ledger posting switched on. Otherwise it stays a payment record, and posting stays explicit, or a rule you write yourself.

How it fits the rest of AxisIQ

Payments is not a bolt-on with its own customer list. Invoices, customers and the payment records are ordinary records in the same workspace as your orders and stock — see Operations — so a payment is searchable, reportable, answerable by Ask Axis, and covered by the same audit trail as everything else. For setup step by step, follow Collect payments online.

One distinction worth stating: this is not your AxisIQ bill. Billing is what AxisIQ charges you for the platform, on our account. Payments is what you charge your customers, on yours.

FAQ

Can my customers pay by UPI? Yes. UPI, cards, netbanking and wallets are available on the hosted payment page, subject to what your provider account has enabled.

Does AxisIQ hold or touch my money? No. Funds move from your customer into your own provider account and settle to your bank on your provider's schedule. AxisIQ creates the link and records the outcome.

Which payment providers does AxisIQ support? Razorpay today, using your own keys. The connection model is provider-pluggable, so a second provider is an addition rather than a rewrite — but one is what is available now.

What happens if the payment notification never reaches AxisIQ? Open the link and hit Refresh — AxisIQ asks your provider for its current state and settles it there and then. Duplicates are safe too: settlement is keyed on the provider's payment id, so a repeat does nothing.

Can I create a payment link directly from an invoice? Yes. Choose an invoice record when creating the link and the amount and customer details prefill from it. The payment record then points back at that invoice, though its status changes only when you or an automation you set up changes it.