UAT (User Acceptance Testing)
The final phase of testing where real users validate that a payment system or feature works as intended before going live.

User acceptance testing, or UAT, is the last stage of testing before something goes live, and the stage where people who will actually use the system try it out. All the testing before it asks whether the software works. UAT asks something else: does it do the job the business wanted. Those are not the same. A build can pass every technical test and still fail here, because the thing it does correctly turns out not to be the thing anyone needed.
In payments the stakes make this stage worth doing properly. A bug in a checkout does not produce a tidy error in a log. It produces a customer who cannot pay, a refund that goes to the wrong card, or a settlement file the finance team cannot read. Card scheme rules ask for certain flows to be tested and signed off before they carry live traffic, with the Visa Core Rules as the public reference. The standards that govern handling card data sit in the PCI Security Standards Council library.
Who Actually Does The Testing
The clue is in the name and it gets ignored anyway. UAT is for the users: the support agent who will issue refunds, the finance clerk who will reconcile, the shop manager who will take a payment at the counter. Engineers testing their own work is useful and it is not UAT. They know what the system expects, so they steer around the paths a real person walks straight into.
What Gets Tested In Payments
The list is longer than the happy path. A sale that works, yes. Also a refusal, a part refund, a full refund after settlement, a double submit, a customer who shuts the browser halfway, an expired card, a foreign card, a soft decline and then a retry, and a webhook callback that turns up twice. Each of these happens weekly in production and each deserves a scripted test.
The Sandbox Problem
Most UAT pain traces back to the sandbox. One that does not act like the live system will pass things that later break, and the gaps sit in the awkward corners: timing, retries, when a webhook turns up, and the exact wording of error codes. Ask the provider in writing which of those differ between sandbox and live. It takes half an hour and it decides how much the testing is worth.
Writing A Script People Will Follow
A good test script reads like instructions to a colleague, not a specification. Each case says what to do, what to use, and what should happen, in plain language with a place to record the result. Vague steps produce vague results, and a tester who is unsure what success looks like will tick the box. Numbering the cases counts too, since a bug report that says the third refund test failed can be run again, and one that says refunds are broken cannot.
Test Cards, Not Real Ones
Providers hand out test card numbers that force a set outcome: a yes, a no, a named error, a challenge screen. Those are what belongs in a UAT script. Staff using their own cards is a recurring problem: it costs them real money, it produces real refunds to unpick, and it cannot produce the failure cases the script needs. A printed list of test cards next to the tester solves most of it.
When It Finds Something Late
Finding a defect in UAT is the system working, even though it does not feel that way with a launch date approaching. The useful discipline is deciding in advance what counts as a blocker and what can ship with a note. A payment that takes the wrong amount is a blocker. A label out of place is not. Teams that settle that question before testing starts argue about one defect; teams that do not argue about all of them.
Sign-Off And What It Covers
Sign-off is a statement that the cases in the script passed, and nothing wider. It is not a warranty that the system is correct, and treating it as one is how a business ends up surprised by something nobody thought to test. Recording what was tested, by whom, and on which version is worth doing, because the question of what was covered tends to be asked after a problem rather than before.
Running A Payments UAT Well
Write the script before the build is finished, since writing it tends to surface questions the specification left open. Put real users on it, with test cards, in a sandbox whose gaps from live are written down. Cover the refusals and the awkward paths at least as thoroughly as the sale. Test the reports as well as the payment, because a settlement file nobody can read is a bug too. Agree the blocker threshold in advance and record who signed off on what version. Keep the script, because the next release can reuse most of it. Pair it with A/B testing in payments once the thing is live, since the two answer different questions. This breakdown of the 8-step payment gateway flow shows which steps need their own cases, and the payment gateway product is designed to give a sandbox that mirrors live behaviour.
Frequently Asked Questions
The people who will use the system day to day: support agents, finance staff, counter staff. Engineers testing their own work is useful but it is a different exercise, since they steer around the paths a real user walks into.
Earlier testing asks whether the software behaves as specified. UAT asks whether it does the job the business actually wanted. A build can pass every technical test and still fail acceptance because the specification itself was wrong.
No. Providers issue test card numbers that force specific outcomes such as approval, refusal or a challenge, which is what a script needs. Staff using their own cards costs real money, creates real refunds and cannot reproduce failure cases.
Refusals, part refunds, refunds after settlement, duplicate submissions, abandoned sessions, expired and foreign cards, retries after a soft decline, and webhooks arriving twice. Those are the cases that occur weekly once live.
By deciding in advance what counts as a blocker. A payment taking the wrong amount stops a launch; a misplaced label does not. Agreeing that threshold before testing starts turns a general argument into a specific one.

Still Have Questions?
Let’s Find the Right Solution for You
Stay Connected with Us!
Follow us on social media to stay up to date with the latest news, updates, and exclusive insights!


