- Reference
58213- Status
- Payment pending
- Amount
- €84.95
Use case · Finding one payment
A customer says they paid. Can you find the transaction in minutes?
Customer care has an order number. The payment provider knows the payment by another reference, the bank by a batch. The payment is rarely missing. It is filed under a name nobody in the conversation has.
“I paid for order 58213 on Saturday evening. Your site still says the order is unpaid.”
Search each system for order 58213. Each search adds the minutes it takes.
Illustrative ticket. The minutes are an example, not a measurement.
Why it hides
One payment, three names. None of them is wrong.
“Identifier misalignment is the most persistent cause: the order system assigns one reference, the payment provider assigns another, the ERP uses a third. Without a shared key, automated matching fails.”
From the Actuals blog

Three systems, one payment. Press the button to link the three records.
- Reference
K7Q2M9X4T1B8R5W3- Status
- Authorised, captured
- Amount
- €84.95 minus fee
- Reference
Payout 14 Oct- Status
- Credited as one batch
- Amount
- €96,412.10, 1,284 payments
Illustrative records. The 16-character provider reference next to a numeric order ID is the example the Actuals blog gives for mapping errors.
“Chasing ‘missing’ payments that aren’t missing. They’re just hiding behind bad formatting and inconsistent logic.”
When the status never arrives
Paid at the provider. Unpaid in your shop.
Your shop hears about a payment through a webhook, a message the provider sends to your systems. If your side does not answer, the provider tries again for a while. Then it stops.
Pick a provider and drag to set how long your side is unreachable. The timeline shows if the payment status still gets through.
How Actuals handles it
Find it once. Then hear about the next one first.
Actuals matches orders, payments, settlements and bank credits at transaction level, every day. A payment that succeeded at the provider but not in your backend becomes an alert, for the team that has to act on it.
- “Immediate mismatch detection, explanation, and resolution on a daily basis”
- “Clear separation between bulk issues and true exceptions”
- “Structured workflows for collaborative investigation”
From actuals.io/product
Pick a team to see which alerts land with them. Click an alert to see what happens next.
Illustrative alerts. The operations alert follows a pattern from the gaming case on this site.
From the customer files
Three teams that stopped searching and started getting told.
Parking & mobility paymentsFlowbird“Its outputs feed transaction orchestration, trigger alerts when payments fail, serve as a foundation for payment processing and support daily matching and accounting entries.”
Read the Flowbird story
Gaming & bettingA listed betting companyActuals flagged groups such as 50 transactions that worked on the payment side but failed on the operator side, so developers could fix the code before the issue scaled.
Read the gaming story
Team members can “search for and view transactions without the usual data cleaning or combining hassles.”
Read the Helloprint storyLooking for one payment? The 15-minute Actuals scan shows where your order, provider and bank references stop lining up.


