Project
Centurion Lab
A useful payment note for a Centurion lab where order progress depends on clean customer references and verified receipt.
How Centurion Lab moves through a real payment week
Centurion Lab is an example for a Centurion lab where progress depends on clean customer references and verified receipt of funds.
For Centurion Lab, start with the rail used for payment and the point where work stops. A pathology or screening order usually waits on a usable customer reference, matched amount, and proof that funds reached the right account. PayShap caps, Instant EFT proof screens, DebiCheck authority checks, and power cuts around Centurion all affect when samples, reports, or collection slots can move.
Include the first payment screen and the order view that shows the customer reference exactly as captured. Lab teams often need one note for reception, one for finance, and one copy saved with the disputed payment. When a specimen, booking, or report is tied to the wrong reference, the queue backs up long before anyone sees the bank response.
Centurion lab payment pack
This example should leave the lab team with wording for the payer, a checking order for staff, and a simple rule for holding or releasing progress. Reception can see what to ask for, accounts can see what to verify, and operations can see what remains blocked. The focus is not on every bank feature, but on the exact checks that stop a Centurion Lab order from moving.
Link Centurion Lab to the closest Playbooks note and a Signals entry only after the failed checks are listed in order. Before any test slot, collection, or report release is approved, compare the bank-side status with the reference typed by the customer, not the one staff expected to see. If you use the contact form, say the query is for the Centurion lab and add screenshots of the order page, proof of payment, and the bank result shown to the team.
- Reference checks tied to lab order states
- Receipt proof saved before sample release
Checks that matter in Centurion
A Centurion lab may take card-linked payments, Instant EFT, PayShap, or debit authority collections depending on the order type. Each one leaves different proof, and staff need to know which proof can support a booking, a walk-in collection, or a report handover. Where DebiCheck is involved, the note should state whether the mandate was authenticated and whether the debit run is separate from the service date.
Reception traffic changes how much explanation a customer can absorb at the counter. Load-shedding can interrupt banking apps, receipt printing, and the moment finance checks a reference against the statement feed. If a courier cut-off or doctor collection time is in play, the lab needs a written hold point instead of verbal assumptions about payment arrival.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Centurion Lab briefing points
Brief the Centurion Lab case with order screenshots, payment timing, and the checks that have already failed. Keep the subject line direct.
Build the note around screenshots that show where the payment trail breaks. One image should show the order status, another should show the proof supplied by the customer, and a third should show the bank confirmation or missing match. That gives Centurion Lab a usable note for disputes, handovers, and queue control on the next similar order.
What our Real-Time Payments customers say
Verified Google reviews