Recommended introduction · 7 minute read

Getting started with VeriFlow testing

Worth reading before your first test. It covers what the work is, how a test runs, the one mistake that costs people their payment, and how you get paid. A seven-question safety check at the end helps you review the most important rules. Confirm your email address to take a test from the board.

What the work actually is

You go through a real customer journey on a partner platform the way any new customer would, and then report what happened — what was clear, what was slow, what was confusing, where you got stuck.

Which journey it is changes from test to test. Creating an account and confirming who you are. Filling a basket and going as far as the checkout screen. Finding something that should be easy to find. Trying a feature that has just launched. We test a wide range of things across a wide range of services, and your brief always says which one this is. Where a step would take real money, the test stops before it — you never pay for anything.

Companies pay for this because these are the steps where real customers give up. Someone who abandons a checkout is a customer the platform never gets, and a team cannot see its own flow with fresh eyes after building it. You can.

Every platform we work with knows about the testing and has commissioned it, and before you accept anything you are told which platform is involved, what is required and what it pays. If no time estimate is shown, ask your manager before taking the test.

Use your real details — this is where people lose their payment

This is the most common reason a test fails, so it comes early.

Most regulated platforms confirm that a new account belongs to a real, eligible person. That check compares what you typed when registering against what you later confirm. If the details you enter are invented, or belong to someone else, the check will not pass — and there is nothing anyone at VeriFlow can do about that, because it is the platform’s own system making the decision, not ours.

Everything you enter goes directly into the platform being tested, as part of its own process. VeriFlow does not receive it.

So: register as yourself, with details that are accurate, and keep them consistent through the whole flow. A test completed as somebody else is not a test — the result tells the client nothing, and it cannot be paid.

Some tests ask you to register with a dedicated test address instead of your personal inbox. This lets the development team safely reproduce different registration and account scenarios and confirm that each path works as expected. Your brief will always tell you when to use it.

Your test address

Create the address once in Account → Your test account, then use it only when a brief asks you to. Its password is generated privately and displayed in your tester account; your manager and other testers cannot view it.

Never send the password through chat. Nobody at VeriFlow will ask you for it. If you ever need a new one, ask your manager to reissue it and it will appear in the same place.

Where a test ends

Your brief lists what is being tested, and the test is finished once you have been through everything on that list. The finish line is written down before you start, so you are never left guessing whether you are done.

Where a step would become real — a payment, an order, an agreement — you stop there. That last step is where the test ends, not where it fails.

You never spend your own money. Not at any stage, not on any test — no deposits, no top-ups, nothing you get back later. If a test ever seems to ask you to pay, that is the moment to stop and message your manager.

Sometimes something outside your control gets in the way: a page will not load, a step is broken, the flow stops halfway. That is not the same as an unfinished test. Tell your manager what happened and where it stopped — cases like that are looked at individually.

Your passwords stay yours

During a test you will create logins and enter codes on the platform’s own screens. That is ordinary use of a service and it is completely fine — the same thing you do on any site you sign up to.

What you never do is pass any of it on. Not to your manager, not to us, not to anyone who messages you, however official they sound. Nobody at VeriFlow will ever ask you to hand over a password, a banking login or a one-time code, and being asked to is itself the problem — stop and report it from the Messages tab.

Some tests include recovery itself: the team running the test resets the password on purpose so that you go through getting back into the account — that is the thing being measured, and your manager walks you through it.

Whatever the step, one rule does not change: you do not send a code, a password or a login to anybody.

Finish what you start

A test has to be completed in full, and this is worth understanding rather than just accepting.

Clients ask for a whole journey — registration and the checks that follow it. If people stop halfway, we end up with twenty completed registrations and ten completed checks, and the second half cannot be reconstructed, because those later steps only exist on top of the earlier ones. A partial run is not half a result; for the client it is no result.

So a test left unfinished counts as not done and is not paid. The brief tells you exactly what the run involves before you accept it — if anything about it gives you pause, simply do not take it. Declining costs you nothing and is always fine.

One test at a time

You hold one test at a time. Once it is submitted for review you can take the next one. Two flows at once is harder than it sounds, and doing one properly is worth more to you and to us than doing two badly.

How a test runs

1. Read the brief and accept. It states the platform, the steps and the pay. Check the time estimate; if it is missing, ask your manager before accepting.
2. Complete the preparation shown on the test card. If a corporate test email is required, copy and confirm that exact address before registering. A personal or different address will not work for that test.
3. Start as the card instructs. Most tests can be followed independently. When a live start with your manager is required, the card says so and stays locked until your manager opens it.
4. Complete the flow. Work through it as an ordinary new customer would, at normal speed and without shortcuts. Messages remain available whenever you want help.
5. Write your report and submit. The form lists the parts of the test; cover each one. On a staged test, stop after each submission until the next stage opens.

If a test has an agreed start time and you are not there, your place is held for one hour and then goes back to the board. Self-guided tests do not use this appointment rule.

Your report

The report is what the client is actually paying for, and it is simpler than people expect. The form lists each part of the test separately, and you write a few sentences under each.

For every part, say how it went: whether it worked, whether anything was unclear or slow, and what exactly went wrong if something did. Plain language is perfect — no report style, no jargon. Screenshots are optional and always welcome when something looked broken.

Short is fine. Empty is not: “all good” on its own tells the client nothing and is the usual reason a submission comes back.

Getting paid

Tests pay €15–€40 and usually take 40–60 minutes. We review submitted work within a day in the normal course of things, and within two days at the outside.

Once accepted, the payment is added to your balance. Payment is by bank transfer to your own account, sent within two working days of a valid withdrawal request. Real money — never vouchers, points or gift cards.

The minimum withdrawal is €15. Anything below that stays in your balance and carries over, so nothing you earn is lost. You enter the account holder name and IBAN in your own account area when you are ready to withdraw — never send payment details through chat.

Bonuses exist and are agreed with your manager: a genuinely detailed report, a real bug found, consistently quick and careful work. They are not promised with every test, but they are real.

If something does not feel right

Stop, and message your manager from the Messages tab. Taking part is optional at every stage: you can decline a test before starting it, and you can stop one you have started.

If a test is not accepted you are told why, and you can ask your manager to look at it again. Disagreeing with a review costs you nothing.