Overview
BPAY requires a Customer Reference Number (CRN) to identify each payer and reconcile transactions accurately.
This guide explains how Payments2Us supports BPAY CRN generation, including the MOD10V01 validation rule, length configuration, sample requirements, and known updates.
This article applies whether you’re setting up BPAY directly or via Ezidebit.
Payments2Us connects directly with BPAY’s API, and does not rely on Ezidebit’s CRN generator.
1. CRN Generation in Payments2Us
Payments2Us does not use Ezidebit Online to create Customer Reference Numbers.
Instead, Payments2Us uses BPAY’s official APIs to generate and validate CRNs.
MOD10V01 Rule Support
Payments2Us fully supports the MOD10V01 algorithm, which is the standard validation rule used by BPAY.
This ensures that all generated CRNs are compliant and verifiable by financial institutions.
You can see an example of MOD10V01 in action in the BPAY Customer Reference Number setup guide:
🔗 How to Set Up BPAY Customer Reference Numbers
2. CRN Length
By default, Payments2Us uses the Membership Number field on the Contact record as the base value for the CRN.
Base number: typically 8 digits
Check digit (MOD10V01): adds 1 additional digit
Total CRN length: 9 digits
The CRN length can be customised if required, but 9 digits is the most common configuration across BPAY implementations.
3. Fixed vs Variable Length CRNs
CRNs can be either fixed or variable in length.
Payments2Us provides flexibility to support either type.
However, fixed-length CRNs are strongly recommended for consistency and ease of reconciliation with your bank and accounting systems.
Most organisations choose fixed-length CRNs unless there is a specific operational need for variable lengths.
4. Sample CRNs for Onboarding
When applying for BPAY setup, your payment provider (e.g. bank or Ezidebit) may request sample CRNs to verify your configuration.
You can generate compliant CRNs using BPAY’s official online tool:
🔗 BPAY CRN Generator Tool
Typical request:
Provide 10 sample CRNs for each variant or length.
Ensure that 1 per 10 ends in 0 for the check digit.
These samples help your provider confirm that the CRN logic and validation rule (MOD10V01) are correctly implemented.
5. Known Issue – CRN Generation Update
BPAY has made changes to how CRNs are generated, which currently affects Payments2Us’ internal CRN generation logic.
Our development team is aware of the issue and is implementing a fix in version 11.1 of Payments2Us.
This enhancement will ensure full alignment with BPAY’s updated CRN specification.
Temporary workaround:
You can generate CRNs externally (using the BPAY CRN Generator Tool) and then upload them to Salesforce using Data Loader.
Once your BPAY or Ezidebit setup paperwork is complete, this fix should be available shortly after the release of version 11.
6. Summary Table
| Configuration Area | Details |
|---|---|
| CRN Source | Generated using BPAY API (not Ezidebit) |
| Validation Rule | MOD10V01 |
| Typical Length | 8 base + 1 check digit = 9 digits |
| Fixed or Variable | Supports both; fixed recommended |
| Sample Requirement | 10 per variant/length, 1 per 10 ending in 0 |
| Known Issue | Temporary BPAY generation change (fix in v11.1) |
| Temporary Workaround | Use BPAY CRN Generator Tool + Data Loader |