Updated
Use case · Admin Panels & Back Offices
Payments back office
Transactions, payouts, refunds and disputes in one console, with reconciliation against the payment provider.
What is a payments back office?
A payments back office is the internal console a finance or operations team uses to see and manage money moving through a product: payments, payouts, refunds and disputes. It keeps a searchable ledger, compares it with the payment provider's own reports, and flags anything that does not match so that a person can resolve it.
When it is needed
A company needs one when transaction volume makes the payment provider's dashboard too slow to work from, when money passes through more than one provider, or when a platform holds or routes funds on behalf of its own customers. At that point reconciliation by spreadsheet becomes the bottleneck at every month end.
What it includes
- A searchable ledger of payments, payouts and refunds
- Reconciliation against provider reports, with mismatches flagged
- A dispute queue with evidence and deadlines
- Approval steps for refunds above a set amount
Before the build
Decisions to make early
Whether to keep an internal ledger
A ledger of your own, recording every movement as an entry that is never edited, makes reconciliation possible. Relying on the provider's data alone ties you to its view of events.
Who may move money
Refunds and manual adjustments need limits and, above a set amount, a second person's approval.
How mismatches are handled
Decide who owns an unmatched item, how long it may stay open and what closes it.
What tends to go wrong
- Storing amounts as floating-point numbers instead of whole numbers of the smallest currency unit, which introduces rounding errors.
- Treating a webhook as the record of a payment, when webhooks can arrive late, twice or not at all.
- Allowing ledger entries to be edited instead of corrected with a new entry.
Where it fits
Typically connects to
- Stripe
- Adyen
- Xero
- PostgreSQL
Teams that use it
- Finance
- Operations
Industries
Terms worth knowing
Services involved
FAQ
Payments back office: questions and answers
What is payment reconciliation?
Payment reconciliation is the process of checking that the transactions a business has recorded match what its payment provider and bank report. A payments back office automates the comparison and lists the exceptions, such as a missing payout, a duplicated charge or a refund recorded on one side only, for a person to investigate.
Does a payments back office have to meet PCI DSS?
A payments back office that never stores or displays full card numbers, and leaves card handling to the payment provider, keeps most card-data obligations with that provider. Which PCI DSS requirements still apply depends on how the business takes payments, so the scope should be confirmed with the provider or a qualified assessor.
Related use cases
All 40 use casesAdmin Panels & Back Offices
Review and approval queue
A queue for the things a person has to check, such as applications, documents or listings, with the decision recorded each time.
Admin Panels & Back Offices
Content management console
An internal console for the content a product runs on, such as listings, courses or catalogue items, with drafts and publishing.
Admin Panels & Back Offices
Customer admin panel
An internal tool for looking up an account, seeing its history and making the changes support and operations make every day.
Build it. Ship it. Grow it.
Book a free 15-minute call. No sales pitch, just an honest conversation about where you are and what it would take to get where you want to be.
Book a call. It's free15-minute call. No commitment.