Every payment source, flowing into one ledger.
Payment Feeds pulls sales from your POS, collections from every UPI provider, card acquirer and payment gateway, payouts from food-delivery and marketplace platforms, and credits from your bank statements. Each line arrives cleaned, de-duplicated and tagged to the right outlet.
| Source | Type | Method | Last file | Status |
|---|---|---|---|---|
| POS - all outlets | Sales | API | 28 Oct 23:59 | Live |
| UPI provider A | Collections | API | 29 Oct 06:10 | Live |
| UPI provider B | Settlement | SFTP | 29 Oct 05:40 | Live |
| Card acquirer 1 | MDR + settlement | Email parser | 29 Oct 07:02 | Live |
| Delivery platform 2 | Payout | CSV upload | 27 Oct | File due |
| Current account | Bank credits | MT940 | 29 Oct 08:00 | Live |
Inside Payment Feeds
POS and billing systems
Bill-level sales with outlet, terminal, shift, tender type and discounts, pulled by API or from scheduled exports.
UPI providers
Collection reports and settlement files from each UPI provider, with UTR, payer VPA (masked) and QR or terminal ID.
Card acquirers
Transaction, batch and MDR files from each acquirer, including card network, card type and GST on fees.
Delivery and marketplaces
Order-level payout statements with commission, packaging charges, ad deductions, TCS and TDS separated.
Bank statements
MT940, CSV, Excel and PDF statements from your current accounts, read line by line and tagged to the right provider.
Cash and petty cash
Shift-close cash counts and bank deposit slips, so cash sits in the same ledger as digital payments.
Four steps, every morning.
Pick your sources
Choose your POS, UPI providers, acquirers, gateways, platforms and bank accounts from the source list.
Connect read-only
Use API keys, SFTP, a forwarding email address or scheduled uploads. No write or payout permissions are ever requested.
Map outlets once
Link each terminal ID, QR, store code and platform listing to its outlet. New terminals are suggested automatically.
Feeds run daily
Files are fetched, parsed, cleaned and de-duplicated every morning before your accounts team logs in.
What happens to each file
- Duplicate lines across re-sent files are dropped
- Date formats, time zones and amount signs are normalised
- Gross, fee, GST and net amounts are split into separate fields
- Masked card and VPA references are kept, full numbers are never accepted
- Missing daily files raise a "file due" alert with the provider name
- Every line keeps a link back to the original file for audit
- Reconciliation software only. It never holds or moves money and uses read-only access.
- AI matches carry a confidence score. Unclear matches go to your accounts team.
- Claims and disputes are drafted for you to send. Outcomes depend on providers' terms.
- Card numbers are never stored, only masked references from providers.
- Data is encrypted and never sold.
About Payment Feeds
What if a provider has no API?
Most providers email or let you download a daily report. Swipellet reads those files from a forwarding address, SFTP folder or manual upload, so every source can be connected.
Do you need our bank login?
No. Bank data comes from statement files or a read-only bank feed set up by you. Swipellet never asks for net-banking credentials.
How far back can we load data?
Load as much history as you have files for. Most teams start with the last three months to catch older short settlements.
The counter is quiet. Every dot is green.
Reconcile your first month free. One month of payments, up to 3 outlets, every feed connected.