Testing UK payment flows brings a wrinkle that purely numeric IBAN countries do not have: the GB IBAN embeds letters. A UK IBAN is 22 characters long and is built from the country code GB, two mod-97 check digits, a 4-letter bank identifier (for example NWBK in the well-known registry example GB29 NWBK 6016 1331 9268 19), a 6-digit sort code, and an 8-digit account number. Any validator worth its salt rejects a GB string whose bank-code positions contain digits, so naive “just random numbers” fixtures break immediately.
Why your test suite needs valid GB IBANs
Three common scenarios. First, form validation: if your frontend uses a proper IBAN library, an invalid fixture makes every test of the happy path fail, and you end up testing your error branch by accident. Second, payment sandboxes: onboarding flows for PSP sandboxes (Stripe, GoCardless, Adyen and similar) often require a syntactically correct IBAN before they issue sandbox mandates. Third, end-to-end tests: a Cypress run that types an IBAN into a Direct Debit signup form needs a value that passes both the client-side and the server-side check, or the test never reaches the screens you actually want to cover.
What “valid” means here
The generator produces GB IBANs that satisfy the ISO 13616 country format (4 letters + 14 digits in the BBAN) and carry correct ISO 7064 mod-97-10 check digits. It runs entirely in your browser, nothing is transmitted or stored, and every generated value is labelled TEST so it cannot quietly masquerade as customer data in a screenshot or bug ticket.
Keep it honest
A structurally valid IBAN is not evidence that an account exists. UK banks run Confirmation of Payee name checks on domestic payments, and EU banks apply Verification of Payee to euro transfers, so a fabricated IBAN gets flagged the moment someone tries to pay it. Use generated GB IBANs in test code, fixtures, demos and documentation, never on an invoice and never to deceive anyone.