Finance · Module
Payments Hub
Links, UPI, mandates, settlements, refunds and payouts through licensed partners
Payments Hub is a planned shared service that routes payment links, UPI QR, mandates, refunds and payouts through RBI-authorised gateways and banks. One3 does not hold funds (verify).
A hub, not a wallet
Payments Hub is planned as a Core shared service from W3 for Billing, Online Store, POS and Collections. It connects to at least two RBI-authorised payment aggregators or gateways, and the tenant connects its own merchant account. Money moves between your customers, the licensed partner and your bank; One3 is not planned to hold funds at any point (verify the regulatory route with counsel). In Year 1, a single gateway's payment links live inside Billing & Invoicing.
Collecting
A payment intent carries the amount, currency, purpose, linked documents (an invoice, order or fee schedule), expiry and an idempotency key. Customers pay through hosted links, a dynamic UPI QR per invoice, or the gateway's hosted checkout for cards, UPI, netbanking and wallets, so no card data touches One3. UPI Autopay and e-mandates are registered through the gateway for recurring charges, with retries inside the rules. Virtual account numbers per customer are planned for matching NEFT and RTGS transfers (verify partner availability).
Reconciling
Webhooks are signature-verified and processed idempotently with ordering tolerance, a dead-letter queue and a replay tool. A daily status job polls the gateway for intents with missing webhooks. Settlement reports are imported line by line: gross, fee, tax on fee, refunds, chargebacks, adjustments, net payout and UTR, so Accounts can match them to bank credits.
Paying out and refunding
Refunds and payouts are R4 Actions: requested, approved by a different person with step-up authentication, submitted to the provider and tracked. Vendor and reimbursement payouts include beneficiary verification through the provider (verify). Chargebacks are recorded with evidence and deadlines. Routing rules choose a gateway by method, amount band, health and preference, with failover to a secondary gateway for new intents.
Features
What Payments Hub includes
Gateway connectors
Adapters for at least two RBI-authorised gateways or aggregators; tenants connect their own merchant accounts.
Payment intents
Amount, currency, purpose, linked documents, expiry and idempotency key for every collection.
Payment links and UPI QR
Hosted links, a dynamic UPI QR per invoice and short links for PDFs and WhatsApp.
Hosted checkout
Cards, UPI, netbanking and wallets on the gateway's hosted pages; no card data touches One3.
Webhook ingestion
Signature verification, idempotent processing, ordering tolerance, dead-letter queue and replay.
Status reconciliation job
Daily polling for intents with missing webhooks.
Refunds
Full or partial refunds with R4 approval, provider submission, status tracking and credit-note linkage.
Settlements
Import gross, fee, tax on fee, refunds, chargebacks, adjustments, net payout and UTR.
Mandates
UPI Autopay and e-mandate registration via the gateway, charge scheduling and retries within rules.
Routing and failover
Route by method, amount band, gateway health and preference, failing over for new intents.
Payouts
Vendor and reimbursement payouts after R4 approval, with beneficiary verification via the provider (verify).
Chargebacks and virtual accounts
Dispute evidence and deadlines, plus customer-specific virtual accounts for bank transfer matching (verify).
Workflow
Settlement to bank match
- 1
Customers pay via link, QR or mandate.
- 2
Webhooks update intents; the daily job catches any missed ones.
- 3
The settlement report is imported with gross, fees, tax on fees and net.
- 4
Accounts matches the net payout to the bank credit by UTR.
Workflow
Issuing a refund
- 1
A refund is requested against a credit note or overpayment.
- 2
An agent can assemble the evidence.
- 3
A different person approves as R4 with step-up.
- 4
The provider processes it and status is tracked.
AI
AI skills and Digital Employees
Settlement anomaly detection
Alerts on missing settlements, fee changes against history and refund or chargeback spikes.
Refund evidence
Prepares the linked credit note or overpayment and references for a human R4 decision.
Chargeback evidence pack
Drafts the evidence pack with its deadline for a human to submit.
Digital Employees that use this module
They act through the same governed Actions as people; risky steps wait for approval.
Frequently asked questions
Does One3 hold my customers' money?
No. Funds move through licensed gateways and your bank; One3 is not planned to hold funds (verify).
Can I use my existing gateway account?
Yes, the plan is for tenants to connect their own merchant accounts with supported gateways.
Can an agent issue refunds or payouts?
No. Refunds and payouts are R4 and always need human approval with step-up authentication.
What happens if a webhook is missed?
A daily reconciliation job polls the gateway for intents without a webhook result.
See Payments Hub in your workflow
Tell us about your team and the outcomes you want. We will walk you through the apps, the Digital Employees and the plan for your industry.