Online payment processing for small business is the ongoing admin behind the pay button: choosing a processor, issuing refunds, answering disputes and recovering failed payments. This article answers what that admin involves week to week on the levelpartner.ai platform, who should own it, and how to pick a processor that keeps it light. If you have not connected a processor yet, the separate guide on card payments covers the first connection.
What a processor does after the payment
Taking the payment is the easy part. After that, the processor holds the funds, pays them out on a schedule, handles refunds you issue, and manages disputes when a client challenges a charge with their bank. It may also hold back part of your balance as a reserve if your account is new or your volume jumps.
All of that lands on someone in your firm. If nobody owns it, refunds get issued twice, disputes pass their deadline and failed retainer charges sit unnoticed for a month.
What to check when choosing a processor
Every processor publishes its own pricing, so compare those directly. Beyond price, these are the questions that matter for a service firm of 10 to 250 staff:
- Is it on the list the platform supports in Payments? If not, it is not an option.
- Does it pay out in your currency, to a bank account in your country, on a schedule you can live with?
- How does it handle disputes, and how long do you get to respond?
- Does it support stored cards and recurring charges with authentication your clients' banks accept?
- Which methods beyond cards does it offer: wallets, bank debits, pay-later?
- Can you export payout reports that your bookkeeper can match to invoices?
Before you start
- A processor connected in Payments and tested with a real payment.
- One named owner for processor admin, with a deputy for holidays.
- Your refund policy written down and published.
- Access to the processor's dashboard for the owner and the deputy.
- Notifications from the processor going to a shared inbox, not one person's email.
How to set up the weekly processing routine
- Route processor notifications for disputes, failed payments and payouts to a shared inbox.
- On the platform, go to Payments, then Invoices & Estimates, click Settings and open Notifications.
- Under Team Notifications, check that Invoice payment failed is switched on, click Manage and edit the template, then click Save.
- Set a weekly calendar slot for the owner to review failed payments, refunds and disputes.
- In that slot, check the processor dashboard for any open dispute and its response deadline.
- Issue agreed refunds from Payments, then Transactions: click the three dots next to the payment, choose Refund and add a note.
- Note each refund and dispute on the client's contact record so the account lead sees it.
Refunds, done once
Issue refunds from the platform so the invoice and the client record update. Refunding from the processor dashboard as well, or instead, leaves the platform showing a paid invoice that has actually been refunded, and finance ends up with two versions of the truth. Agree who may approve refunds and above what value someone senior signs off.
Disputes need evidence, fast
When a client disputes a charge with their bank, the money is pulled back and the processor gives you a deadline to respond. Your best evidence is already on the platform: the accepted estimate or contract, the invoice, the emails and calls on the contact, and proof the work was delivered. Gather it into one response, send it before the deadline, and call the client. Many disputes are simply a client who did not recognise the name on their statement.
Suppose the agency charges 30 retainers to stored cards each month and two or three fail because cards have expired. If nobody notices until month-end reconciliation, that money arrives three or four weeks late. With the failed-payment team alert switched on and the account lead calling the client the same day, most of those charges could be recovered within a few days. The counts are illustrative.
What it costs you in time
For a firm taking a few hundred payments a month, the weekly routine takes about half an hour. A dispute adds an hour to gather evidence. Without the routine, the same work still happens, but later, under deadline, and usually by whoever happens to notice.
The mistake most people make
Picking a processor only on headline fees. A slightly cheaper processor that pays out slowly, freezes funds without warning or gives you little time to answer disputes costs more in cash flow and staff time than it saves. Weigh payout timing and dispute handling as heavily as price.
When to keep processing simple
If almost all your clients pay by bank transfer and cards are an occasional convenience, you do not need a weekly routine. Check the processor dashboard monthly and handle anything that comes up. Build the routine once recurring card charges become a real share of revenue.
Troubleshooting
The processor has placed a reserve on your account. Usually triggered by a jump in volume or a new account. Contact the processor, explain the change and provide any documents they ask for.
A refund shows on the processor but the invoice still shows paid. It was issued outside the platform. Record the refund on the invoice so the records agree.
A dispute deadline was missed. The notification went to one person's inbox. Route alerts to a shared address and give the deputy access.
Failed payments are not alerting anyone. The team notification for failed invoice payments is switched off, or it goes to someone who has left. Check it under Notifications in the invoice settings.
Related guides
For the first connection and how a card payment flows, see connecting a card processor. For matching payouts to invoices in your books, see the month-end reconciliation routine. To automate the wider chase, read the invoice workflow guide.
Frequently asked questions
Can I switch processors later?
Yes, but stored cards usually stay with the old processor. Plan a migration with the new processor or ask clients to re-enter their card on the next invoice.
Who should own payment processing?
One named person in finance or operations, with a deputy. Account leads should see refunds and disputes on the contact record but not run the admin.
How do I reduce disputes?
Use a business name on statements that clients recognise, send clear invoices, and get written consent for recurring charges. Most disputes come from confusion, not fraud.
Should I offer pay-later options?
Only if your clients ask for them and your processor supports them. For most B2B service firms, cards and bank transfer cover the need.