Modulus Checking
Technical validation of account structure
- Validates sort code & account number
- Mathematical algorithm verification
- Catches typos & format errors
- Does not verify account holder name
From 1.5p per check (volume pricing)
Two complementary checks for UK payments: technical account validation with Modulus Checking, and name verification with Confirmation of Payee (CoP). Pick the right level of assurance for each payment.
Confirm payment details are accurate and belong to the intended recipient. In the UK, two complementary approaches support security, accuracy and fraud prevention.
Why validation matters: Payment fraud costs UK businesses millions annually. Confirmation of Payee is widely used across UK payments to verify account holder names. Proper account validation reduces fraud, prevents misdirected payments, and improves payment accuracy.
Start with technical checks for every entry, then add name verification where risk or regulation demands it.
Technical validation of account structure
From 1.5p per check (volume pricing)
Name verification against the account holder
From 15p per check
Modulus Checking confirms "Is this a valid account?" · Confirmation of Payee confirms "Is this the right person's account?"
Modulus checking uses mathematical algorithms defined by VocaLink (a Mastercard company) to verify that a UK sort code and account number combination is structurally valid.
Confirmation of Payee is a name-checking service that verifies the name you provide matches the actual account holder's name on file with their bank.
Match the validation level to the risk and workflow. Many teams run both in a two-tier setup.
Catch typos and errors as users enter bank details into your forms.
Low cost, instant validation - ideal for real-time feedback during data entry.
A customer is adding a new payee or paying someone for the first time.
Verify the account holder name matches to prevent fraud and misdirected payments.
You're processing large payments where the cost of an error would be significant.
From 15p is negligible next to the risk of a £10,000+ misdirected payment.
Cost-effective validation with stronger checks on high-risk payments.
Step 1: Modulus Check on all entries (from 1.5p) to catch basic errors.
Step 2: CoP (from 15p) only on flagged or high-risk payments.
Validate thousands of existing customer bank accounts in your database.
Cost-effective at volume - quickly finds invalid accounts that need updating.
Try the free online demos to see both services in action. No registration required.
Ready to integrate? Sign up and receive 5 free credits to test against our live environment.
Sign up for 5 free creditsQuick answers about modulus checks, CoP, pricing and how to combine both services.
Modulus Checking validates the technical accuracy of a sort code and account number combination using mathematical algorithms. It confirms the account structure is valid but doesn't verify who owns the account.
Confirmation of Payee (CoP) goes further by checking that the name you provide matches the actual account holder's name on file with their bank. Use Modulus Checking for basic validation; use CoP when you need to verify the recipient's identity.
Use Modulus Checking (from 1.5p with volume pricing) for: validating account details during data entry, checking account format before storing in your system, reducing typos and basic errors, high-volume low-risk transactions.
Use Confirmation of Payee (from 15p) for: new payee setup, high-value payments, first-time payments to unfamiliar recipients, fraud prevention in payment workflows, and reducing misdirected payments.
Yes. Many customers use a two-tier approach: first run Modulus Checking to validate account structure and catch basic errors (low cost), then run Confirmation of Payee for name verification on flagged or high-risk payments. This optimises both cost and fraud prevention.
Confirmation of Payee is widely used by payment service providers to combat Authorised Push Payment (APP) fraud. While requirements vary by business type, implementing CoP demonstrates due diligence and significantly reduces fraud risk.
A CLOSE_MATCH means the name is similar but not identical (e.g. "Selena Gome" vs "Selena Gomez"). Our API returns the actual account holder name so you can present it to your user for confirmation. This helps catch typos while still allowing legitimate payments to proceed with user approval.
Both services deliver real-time responses in under 50ms on average, making them suitable for synchronous validation in web forms, mobile apps, and payment workflows without impacting user experience.
Yes, we offer tiered pricing for high-volume customers. Contact our sales team to discuss enterprise pricing, SLA options, and dedicated support packages tailored to your validation needs.