[Delete] Payouts, disputes and reporting & Transactions and payment links
Old article - Payouts, disputes and reporting {toggle="true"}
Once payments start moving through Lupa Pay, the **Payouts**, **Reports** and **Disputes** tabs are where you check that the money's actually landed, pull the numbers your accountant needs, and respond when a client's bank challenges a charge. Each tab is a focused view from our payments partner, embedded inside Lupa, so a Practice Manager can see everything they need without a separate processor login.
π‘ In short: Payouts = bank transfers that have left Lupa Pay for your account. Reports = downloadable summaries for accounting and reconciliation. Disputes = chargebacks raised by clients' banks that you may need to respond to.
π Visible only when Lupa Pay is enabled for your store, and only to users with the Lupa Pay permission. If Lupa Pay isn't in your side nav, or these tabs render "Lupa Pay is not enabled", see .
--- ## Where they live Open **Lupa Pay** in the side nav. The page has five tabs:
πΈ Drop in screenshot: ~/Desktop/lupa-pay-screenshots/pdr-tab-strip.png (the Lupa Pay page tab strip showing Transactions, Reports, Disputes, Payouts and Payment Links).
This article covers **Payouts**, **Reports** and **Disputes**. The other two are documented separately:
Tab | Where it's documented |
Transactions / Payment Links | |
Payouts / Reports / Disputes | This article |
βΉοΈ These three tabs are rendered by our payments partner inside Lupa. That means the controls, columns, filters and downloads are theirs β Lupa hosts the experience but doesn't change it. If you've used a payments dashboard like Stripe or Adyen elsewhere, the layout will feel familiar.
--- ## Payouts A **payout** is the bundled bank transfer Lupa Pay sends to your business account. It's *not* one row per client payment β payouts group many transactions together (minus fees and refunds) into a single settlement that lands in your bank as a single line item. This is what matters for end-of-day reconciliation. ### When to use the Payouts tab - **Reconciling your bank statement.** Match each line on your statement to a payout in Lupa Pay. - **Spotting a missed payout.** If you usually see a Friday payout and Friday's missing, this is the place to confirm whether it's pending, delayed or simply hasn't been initiated. - **Tracing a payout back to the underlying transactions.** Click into a payout to see the individual payments that made it up β useful when your accountant queries the gross-vs-net difference. ### Reading a payout Each payout typically shows:
Field | What it means |
Status | Whether the transfer has been initiated, is in transit to your bank, has settled, or has failed |
Net amount | The figure that actually lands in your bank β gross transactions, minus refunds, minus processing fees |
Reference / ID | The reference your bank will show against the deposit. Use this to match the payout to a line on your statement |
Period | The transactions covered by this payout |
πΈ Drop in production screenshot: ~/Desktop/lupa-pay-screenshots/pdr-payouts.png (the Payouts tab populated with at least a couple of recent settlements). Local dev shows an error state because real settlement data only exists in the production payments environment β capture this from a live store.
β Reconcile weekly, not monthly. A 7-day cadence keeps any mismatch β a missing line, a fee surprise, a dispute hold β recoverable. By the time you spot it 30 days later you may already be chasing it through three separate exports.
--- ## Reports The **Reports** tab is the place to download structured exports of your Lupa Pay activity for accounting, audit and tax purposes. Think of it as the "give-this-to-your-bookkeeper" tab β anything more detailed than what's on the Payouts tab. ### When to use the Reports tab - **Month-end close.** Pull a settlement report covering the period and hand it to your accountant. - **Year-end / tax prep.** Download a full-year fee breakdown so the gross-to-net path is auditable. - **Investigating an unexpected charge.** If a payout net total looks wrong, a fee report often shows the missing piece (refund fees, dispute fees, currency conversion). ### What you can typically download The reports available depend on your account configuration with our payments partner. Common ones include:
Report | Use it for |
Settlement / payout report | Reconciling each bank deposit against the transactions inside it |
Transaction report | Listing every payment, refund and adjustment in a period β the "raw data" view |
Fee report | Breaking out processing fees, dispute fees and any other deductions |
Reports download as **CSV** files in your browser. Open them in Excel, Google Sheets or your accounting tool of choice.
πΈ Drop in production screenshot: ~/Desktop/lupa-pay-screenshots/pdr-reports.png (the Reports tab showing the available report types). Capture from a live store β local dev cannot render real reporting data.
π‘ Need a transaction-by-transaction view inside Lupa, not a CSV? Use the Transactions tab for searchable, filterable detail β see . Reports is for exporting; Transactions is for browsing.
--- ## Disputes A **dispute** (also called a *chargeback*) is when a client asks their bank to reverse a Lupa Pay charge β typically because they don't recognise the payment, claim the goods/service weren't delivered, or believe their card was used fraudulently. The bank notifies our payments partner, who notifies us, and the practice has a fixed window to respond with evidence.
β οΈ Time matters. Disputes have a hard deadline (often 7β14 days from when the dispute is opened, depending on the card scheme). If you don't respond by the deadline, you automatically lose and the funds are taken back permanently β plus a dispute fee. The Disputes tab surfaces the deadline; treat it as a same-week task.
### When to use the Disputes tab - **Daily glance** to catch new disputes early β ideally part of an end-of-day routine for whoever owns finance. - **Responding to a dispute** by uploading evidence (consent forms, signed estimates, proof of services rendered, communication trail). - **Tracking the outcome** β whether you won, lost, or the client withdrew the dispute. ### How a dispute moves The exact stage names vary slightly between card schemes, but every dispute follows roughly this shape:
Stage | What's happening |
Needs response / Action required | The client's bank has raised the dispute; the practice has a fixed window to upload evidence |
Under review | You've submitted evidence; the bank and the card scheme are deciding |
Won | The dispute was resolved in your favour and the funds stay with you |
Lost | The dispute was resolved against you, and the disputed amount (plus any dispute fee) is debited from your next payout |
Accepted | You chose to accept the dispute without responding β equivalent to lost, but you skip the evidence step |
πΈ Drop in production screenshot: ~/Desktop/lupa-pay-screenshots/pdr-disputes.png (the Disputes tab with at least one open dispute showing its deadline and reason code). Capture from a live store.
### Responding to a dispute The exact form is rendered by our payments partner inside the tab and is shaped by the card scheme's evidence requirements. Broadly, you'll be asked to: 1. Confirm the **transaction details** (amount, date, who paid, what was paid for). 2. Upload **evidence** β anything that proves the service was authorised, delivered, and what the client expected. Common evidence: - Signed consent or estimate forms - The clinical record or invoice line for the visit - Email/SMS communication confirming the appointment or payment - Photographs of any goods collected (e.g. medication signed for at the desk) 3. Add a short **written explanation** (a paragraph is fine β bank reviewers skim). 4. Submit. The dispute moves to *Under review* and you can't edit further.
β Strong evidence usually wins. Banks decide on documentation, not opinion. A consent form with the client's signature against the exact services billed is the single most effective piece of evidence in a vet practice context. If you don't take consent in writing today, this is the strongest reason to start.
β οΈ Don't refund the client and fight the dispute. If you decide a refund is the right outcome, issue it from the original payment record (see ) and accept the dispute, or contact our payments partner via Lupa support β running both at once can leave the client refunded twice and you out of pocket.
--- ## Tips
β
- Bookmark the three tabs you actually use. Practice Managers tend to live in Payouts; bookkeepers in Reports; the dispute owner in Disputes. Direct URLs work β /lupa-pay?tab=payouts, ?tab=reports, ?tab=disputes. - Match payouts to bank statement lines weekly. It's the cheapest fraud control you can run, and it spots small fee misunderstandings before they compound. - Use Reports for accounting, Transactions for support queries. Reports give your bookkeeper a deterministic snapshot; Transactions answers "why did this client get charged Β£X?". - Save dispute evidence before submitting. Keep a local copy of the PDFs you upload in the practice's drive β if the dispute is appealed later, you'll want the same files at hand. - For multi-site groups, check each store separately. Each Lupa Pay store has its own payouts, reports and disputes β switch sites in the header to see them all.
--- ## Troubleshooting
Problem | What to do |
The tab shows "Something went wrong... Contact support for help" or fails to load | That message is from our payments partner's embedded component, usually meaning the Lupa Pay session couldn't initialise. Refresh the page once. If it persists, log out and back in β the session token may have expired. If still failing, message Lupa with the Lupa Pay store name and the tab affected |
The Payouts tab is empty | Either you have no settled payouts yet (new accounts can take a few business days for the first payout) or your store has no Lupa Pay activity in the chosen period. Confirm activity in the Transactions tab β if there are recent paid transactions but no payouts, contact Lupa to verify your payout schedule |
A payout's net amount is less than I expected | The difference is almost always processing fees + any refunds in the period. Open the payout to see the included transactions, then download a fee report from the Reports tab for the same period to see the deductions itemised |
The Disputes tab shows a dispute I don't recognise | Click into the dispute to see the underlying transaction (client name, amount, date). Cross-check it against your invoice records. Most "I don't recognise this" disputes are valid charges where the client doesn't recognise the practice's billing name β respond with evidence rather than ignore |
I missed a dispute deadline | If the dispute has moved to Lost, the funds are gone and there's nothing further to do in Lupa. Some card schemes allow a one-off appeal β message Lupa support quickly with the dispute reference; chances are slim but worth trying within 24 hours |
I can't download a report β the button does nothing | Browser pop-up or download blockers will silently swallow the file. Allow downloads from |
The same data looks different in Lupa Pay and in my accounting tool | The two are reconcilable but rarely identical row-for-row. Lupa Pay groups by settlement period; accounting tools usually group by invoice date. Use the settlement report from Reports as the bridge β it's structured for accounting reconciliation |
I see disputes for a previous payment processor I migrated away from | Disputes against your old processor stay in that processor's dashboard, not in Lupa Pay. The Disputes tab here only covers Lupa Pay charges. Contact your old processor for anything pre-migration |
--- ## Frequently asked questions
How often does Lupa Pay pay out?
How often does Lupa Pay pay out?
The default schedule is set during onboarding β most UK practices receive next-day or every-other-day payouts. The exact cadence is configurable; ask Lupa if you want to change it. The Payouts tab shows your actual recent rhythm.
Why is my first payout taking longer than expected?
Why is my first payout taking longer than expected?
New accounts often have a longer initial hold (commonly 7 days from the first transaction) so our payments partner can verify activity. After the first payout, subsequent ones move to your normal schedule.
Where do dispute fees come from and can I avoid them?
Where do dispute fees come from and can I avoid them?
When a client raises a dispute, the card scheme charges a non-refundable processing fee regardless of who wins β that fee is deducted from your next payout. You can't avoid it once a dispute is opened, but strong consent and clear billing names dramatically reduce how often disputes are opened in the first place.
Can I respond to a dispute outside of Lupa?
Can I respond to a dispute outside of Lupa?
No β evidence has to be submitted through the Disputes tab so it reaches our payments partner via the right channel. Anything you send the client's bank directly will be ignored.
What's the difference between a refund and a dispute?
What's the difference between a refund and a dispute?
A refund is initiated by you (see ). A dispute is initiated by the client's bank, typically because the client called their bank instead of asking the practice. If a client has a complaint, refunding them quickly is almost always cheaper and faster than letting it become a dispute.
Can I export reports automatically on a schedule?
Can I export reports automatically on a schedule?
Not yet from inside Lupa. The Reports tab is on-demand β pick the period and download. If you need scheduled exports for an accounting tool, ask Lupa about API access.
Why don't I see Reports / Payouts / Disputes in my side nav?
Why don't I see Reports / Payouts / Disputes in my side nav?
You see the Lupa Pay entry, but the tabs themselves are inside that page β click into Lupa Pay first, then choose the tab. If the Lupa Pay entry is missing entirely, you don't have the Lupa Pay permission on your role; ask a practice administrator.
--- ## Related articles
Old article - Transactions and payment links {toggle="true"}
The **Lupa Pay** page is where you see every transaction the practice has taken through Lupa Pay, and where you can track **payment links** β emailable URLs that let a client pay an invoice online without coming back into the practice. Most days you'll use it for two things: looking up a recent payment when a client queries a charge, and sending a payment link to a client who's collecting tomorrow.
π‘ In short: Open Lupa Pay in the side nav for the Transactions and Payment Links tabs. Create a payment link from an invoice via Add Payment β Online β Create payment link. Refund a Lupa Pay payment from the payment record itself.
π Lupa Pay must be enabled for your store. If Lupa Pay isn't in your side nav, your store either doesn't have Lupa Pay turned on or your role doesn't include the Lupa Pay permission. Setup is covered in .
--- ## Where to find them Click **Lupa Pay** in the side nav. The page has five tabs:
Tab | What it shows |
Transactions | Every Lupa Pay transaction β searchable, filterable, with full payment detail |
Payment Links | Every payment link the practice has created, with its status, client, invoice and a copy/open action |
Reports / Payouts / Disputes | Covered in |
This article covers the **Transactions** and **Payment Links** tabs. Card readers live in . --- ## Viewing a transaction The **Transactions** tab is Lupa Pay's full transaction view. You can: - **Filter** by date range, status, payment method or amount. - **Search** by reference, client name or invoice. - **Open a row** to see the full payment detail β amount, status, fees, payment method, the card brand and last four digits, and any linked refunds. - **Export** the visible list to CSV for accounting.
πΈ Screenshot: the Transactions tab with a date range applied and one row in focus. Save as ~/Desktop/lupa-pay-screenshots/01-transactions.png and drop into this block.
For day-to-day "what did this client pay?" lookups, going via the client's invoice is usually faster β the payment record on the invoice links straight through. Use the Transactions tab when you're investigating across clients or working from a card reference. --- ## Creating a payment link Payment links are generated from an invoice β never standalone. The link routes the client to a hosted Lupa Pay (or Stripe) checkout for the exact invoice amount. 1. Open the invoice you want paid. 2. Click **Add Payment**. The Create Payment dialog opens. 3. Switch to the **Online** tab. 4. Click **Create payment link**. Lupa generates the link and you'll see *"Payment link generated"*. 5. Send it to the client one of two ways: - **Send via email** β sends from your practice email integration with a default subject/body you can edit. - **Copy to clipboard** β paste into SMS, WhatsApp, or wherever else you message the client from.
πΈ Screenshot: the Online tab of the Create Payment dialog after Create payment link has been clicked, showing the generated link and the Send via email button. Save as ~/Desktop/lupa-pay-screenshots/02-create-payment-link.png and drop into this block.
π‘ Send via email is greyed out if the client has no email address on file or your store doesn't have an email integration configured. Hover the button to see which it is, then either add the client's email or paste the copied link into another channel.
When the client opens the link, they're taken to a hosted checkout page in their browser. As soon as they pay, the invoice is settled in Lupa and the link's status flips to **Paid**. --- ## Tracking payment links The **Payment Links** tab is the one place to see what's outstanding and what's been paid.
Column | What it shows |
Created | When the link was generated |
Client | The client the invoice belongs to |
Invoice | The invoice the link will pay β click to open |
Amount | The amount the link will collect |
Provider | Lupa Pay or Stripe, depending on what's configured for the store |
Expires | When the link auto-expires if unused |
Status | Active, Paid or Expired (see below) |
Actions | Copy link and Open link β quick way to re-share or preview what the client sees |
Filter the list by **client**, **status** or **provider** along the top. The **Clear filters** button resets everything. ### Statuses
Status | Meaning |
Active | The link has been generated and not yet paid or expired. The client can still pay through it |
Paid | The client paid through the link. The invoice is settled and a transaction now exists in the Transactions tab |
Expired | The link's expiry date has passed without a payment. It can no longer be paid through. Generate a fresh link from the same invoice if you want to chase the client again |
πΈ Screenshot: the Payment Links tab showing rows in different statuses, with the filter bar visible. Save as ~/Desktop/lupa-pay-screenshots/03-payment-links.png and drop into this block.
--- ## Sending a payment confirmation emailOnce a payment is complete, you can send the client a confirmation email directly from the payment row on the invoice β without going back through the Create Payment flow.1. Open the invoice the payment is recorded against. 2. Find the payment in the payments list. Next to the completed payment, click the **email icon**. - If no confirmation has been sent yet, this opens the email editor with the subject pre-filled as **Payment Confirmation** and the payment amount already populated. Edit the message if you like, then click **Send**. - If a confirmation has already been sent, clicking the icon opens **Email Details** β a read-only view of the email that was sent. 3. You can also reach the same action from the **Payment Details** page for that payment.
π‘ Already sent a confirmation? The icon still works β it switches to showing you the sent email rather than opening the editor again, so you can confirm exactly what the client received.
--- ## Refunding a Lupa Pay payment Refunds are issued against a specific payment record, not against the invoice or the transaction list directly. 1. Open the invoice (or payment record) you need to refund. 2. Click **Create Refund**. 3. Choose a **refund reason** (Sold in Error, Overpayment, Goods Not Collected by Client, Goods Not Received by Client, or Unknown) and add notes if helpful. 4. Confirm.
β οΈ Lupa Pay online payments must be refunded in full. A notice appears in the refund dialog confirming this. If you only need to refund part of the bill, leave the original payment alone and issue a credit note for the difference instead. Manual and terminal payments do support partial refunds.
Refund statuses follow this lifecycle: **Draft** β **Pending** (sent to the processor) β **Completed** (money returned to the client). **Cancelled** appears if the refund is cancelled before it's allocated to a payment or credit note. You can follow the status from the refund record on the payment. --- ## Tips
β - Filter the Payment Links tab by Active before chasing clients. Saves you from re-sending links that already paid or already expired. - Use Send via email when the integration is set up. It's faster and the message is consistent β paste-copy is fine but invites typos in the link if you send from a phone. - Open the link yourself before chasing a client. Open link from the row actions shows you exactly what the client sees, which makes phone troubleshooting a lot easier. - Use Transactions for cross-client queries; the invoice for single-client queries. Going via the invoice page surfaces the related payments and refunds in context.
--- ## Troubleshooting
Problem | What to do |
Lupa Pay isn't in my side nav | Either the store doesn't have Lupa Pay enabled or your role doesn't include the Lupa Pay permission. Ask a practice manager β setup is covered in |
Send via email is greyed out on a payment link | Hover the button β Lupa shows which prerequisite is missing. Usually it's no email address on the client, or no email integration on the store. Add the client's email or copy the link to send via another channel |
The client says the link doesn't work | Open it yourself with Open link in the row actions. If the link is Expired, generate a fresh one from the same invoice. If it's Active but the client still can't pay, ask whether their bank declined β that detail will show on the failed transaction row |
Refund button only offers a full amount | Lupa Pay online payments are full-refund only. Issue a credit note for the difference if you needed a partial. Manual and terminal payments allow partial refunds |
"Payment link copied" toast didn't appear | The browser blocked clipboard access. Click Open link instead, then copy the URL from the address bar |
--- ## Frequently asked questions
Can I create a payment link without an invoice?
Can I create a payment link without an invoice?
No β every payment link is tied to a specific invoice and amount. If you need to take an arbitrary payment, raise a draft invoice first, then generate the link from there.
Does the link expire if the client doesn't pay?
Does the link expire if the client doesn't pay?
Yes. The Expires column shows the date. Once it's passed, the status flips to Expired and the link stops working. Generate a fresh one from the invoice to chase again.
Can I edit a payment link after sending it?
Can I edit a payment link after sending it?
No. Generate a new link if anything about the invoice has changed. The old one will still work until it's paid or expires, so cancel it on the invoice if you don't want it used.
The client paid through Lupa Pay but the invoice still shows unpaid β why?
The client paid through Lupa Pay but the invoice still shows unpaid β why?
The invoice settles automatically when the payment confirms. If there's a gap, refresh the invoice page. If it persists, check the Transactions tab to confirm the payment captured β if it's stuck on Pending or Failed, contact Lupa support with the transaction reference.
Where do I see what hit my bank account?
Where do I see what hit my bank account?
That's the Payouts tab, covered in . Transactions are individual payments; payouts are the bundled bank transfers.
--- ## Related articles
