Think Build Implement Repeat
London, UK +44 7367 067226
WhatsApp FOLLOW f in X
  1. Home
  2. Blog
  3. Our Merchants Keep Emailing Us to Explain Their Payouts. How Do We Stop That?
Problems We Solve

Our Merchants Keep Emailing Us to Explain Their Payouts. How Do We Stop That?

Payments fintechs field merchant emails asking to explain payouts, fees and deductions. We build settlement reports and a merchant view that answers them first.

Updated 2 min readBy SpiderHunts Technologies

Free estimateNo obligation

Get a free estimate

Tell us what you need. A senior engineer reads every enquiry.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →

Quick answer — TL;DR

Merchants email about payouts because the payout arrives as one number and the breakdown of sales, fees, refunds and holds is not available to them in a form their bookkeeper can use. We build settlement reports that reconcile each payout to its transactions, a merchant dashboard view and exports in accounting-friendly formats, so most questions are answered before they are asked.

Why is my payout lower than my sales?

Your merchants take payments through your product and receive a payout every day or week. The payout is less than their sales, for good reasons: fees, refunds, chargebacks, a reserve, a card sale from Friday that settles on Tuesday. The merchant sees one number arrive in their bank account and a different number in their sales screen.

So they email. Your support team pulls transaction lists from the admin panel, works out the payout in a spreadsheet, and sends an explanation. The merchant's bookkeeper then asks for it in a format they can import. Next week, another merchant asks the same thing about a different payout.

Why payouts confuse merchants

Payout breakdowns exist inside your systems. They are just not exposed to the merchant in a form they can use.

  • The payout is linked to a batch at your provider, not obviously to the merchant's sales.
  • Timing differences between sale, settlement and payout are not explained.
  • Fees, refunds, chargebacks and reserves are netted into one figure.
  • Exports, where they exist, are raw transaction lists without payout grouping.
  • Bookkeepers need a format that matches their accounting software, and nobody supplies it.

Support time and merchant trust

Each explanation takes real support time, often from someone who has to learn the payments side to answer. Merchants who cannot reconcile their payouts lose trust, and some leave for a provider whose reports are clearer. Mistakes in the manual explanation create a second round of emails. And if a payout genuinely is wrong, it gets lost among the ones that were only confusing.

Settlement reports merchants can use

What we build turns each payout into something a merchant and their bookkeeper can follow line by line.

  1. Each payout is linked to every transaction, fee, refund, chargeback and reserve movement that makes it up, using your ledger and your provider's settlement data.
  2. A daily check confirms that each payout's components add up to the amount paid, and flags any that do not for ops before merchants see them.
  3. The merchant dashboard shows each payout with its breakdown, and each sale shows which payout it went into.
  4. Exports are offered in formats bookkeepers want, such as CSV layouts that import into Xero or QuickBooks.
  5. Common questions are answered on the payout screen, such as why a sale has not been paid out yet.
  6. Support get the same breakdown in their helpdesk panel, so any question that still arrives is quick to answer.
Payout componentShown to merchant asLinked to
Card sales settledSales included in this payoutEach sale
Processing feesFees by typeEach sale or a fee line
RefundsRefunds deductedOriginal sale
ChargebacksDisputed payments deductedDispute case
Reserve movementsHeld or released amountsYour reserve rule

Payout questions, answered in advance

Merchants open their payout and see where every penny went. Their bookkeeper downloads a file and imports it. Support gets fewer payout emails, and those that come in are answered straight from the panel. Payouts that do not add up are caught by the daily check before a merchant spots them.

Is this happening with your merchants?

  • Merchants email to ask why their payout is different from sales.
  • Support build payout explanations in spreadsheets.
  • Bookkeepers ask for exports in a different format.
  • Your dashboard shows sales and payouts separately.
  • Nobody checks that each payout adds up before merchants see it.

FAQ

Frequently asked questions

The questions readers ask us after this guide.

Still have a question?

Ask us directly — a senior engineer will get back to you.

Ask about your project

Do we need a new ledger to do this?

Not usually. We link payouts to their components using your ledger and provider settlement data.

Can you export directly to merchants' accounting software?

We offer import-ready files, and a direct connection to Xero or QuickBooks can be added if merchants want it.

What if our provider's settlement data is limited?

We use what it provides and fill the gaps from your own records, and we tell you where the gaps are.

Will this reduce payout errors?

The daily check flags payouts whose components do not add up, so they are found earlier. It does not change how payouts are calculated.

What drives the cost?

How payout data is stored today, the number of components and currencies, and the export formats needed.

Keep reading

More on Problems We Solve

Start here

Tell us where your fintech ops team loses the day

Describe the queue or the report that eats your ops team's week, the providers and partner bank you sit on, and the admin tools people use now. We will tell you what we would build, what we would leave to your own engineers, and if a setting in your provider's dashboard already solves it, we will say so instead.

  1. You tell us what you needTwo minutes on the form, or a message on WhatsApp.
  2. A senior engineer reviews itAnd comes back with questions, a realistic range and an honest view on fit.
  3. Free 30-minute scoping callWe talk through scope, options and a realistic estimate — with no obligation.
Free estimateNo obligation

Talk to someone who builds this

Send a short brief and we will come back with an honest view and a realistic range.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →