Purpose
Payreq can support customised QR codes that direct customers to a pre-filled Payreq page. These QR codes can be generated from customer-specific URLs and printed on notices, letters, or other customer communications.
There are two common use cases:
QR code type | Purpose |
Digital subscription QR code | Takes the customer to a pre-filled FastForm page so they can subscribe to receive future notices digitally |
Payment QR code | Takes the customer to a pre-filled Payreq payment page so they can make a payment more easily |
This helps reduce manual entry, improves the customer experience, and makes it easier for customers to take the intended action.
Digital Subscription QR Codes
Overview
A digital subscription QR code directs the customer to a Payreq FastForm registration page.
The URL can be customised so that key information from the customer’s current notice is pre-filled, such as:
Field | Example |
Account Number / Contact ID / Reference Number | 12345 |
Customer name as shown on the bill | Mr S Smith |
The customer still needs to review the form, enter their email/phone details where required, and complete the subscription process.
Example FastForm URL
A standard FastForm URL may look like this:
https://test.payreq.com/fastform/demo-biller/create
A customised pre-filled version may look like this:
https://test.payreq.com/fastform/demo-biller/create?aN=12345&a1=Mr%20S%20Smith
In this example:
URL component | Meaning |
demo-biller | The biller-specific FastForm path |
aN=12345 | Pre-fills the account number/reference field |
a1=Mr%20S%20Smith | Pre-fills the customer name field |
%20 | Encoded space character |
FastForm URL Format
Format:
<Base FastForm URL>?aN=<Account Number>&a1=<Customer Name>
Example using plain values:
https://test.payreq.com/fastform/demo-biller/create?aN=12345&a1=Mr S Smith
Final encoded URL:
https://test.payreq.com/fastform/demo-biller/create?aN=12345&a1=Mr%20S%20Smith
The exact FastForm parameters should be confirmed by Payreq before production use, as FastForms may vary depending on the biller’s configuration.
Payment QR Codes
Overview
A payment QR code directs the customer to a Payreq payment page.
The payment page can already accept pre-filled values in the URL, including:
Field | URL parameter | Example |
Account number / reference number | accountNumber | 1111 |
Payment amount | amount | 100.01 |
This allows a QR code to take the customer directly to a payment page with their payment reference already populated, and optionally the amount as well.
Example Payment URL
A standard payment page URL may look like this:
https://go.payreq.com/pay/tamworth
A pre-filled payment URL may look like this:
https://go.payreq.com/pay/tamworth?accountNumber=1111&amount=100.01
In this example:
URL component | Meaning |
tamworth | The biller-specific payment page |
accountNumber=1111 | Pre-fills the customer’s payment reference/account number |
amount=100.01 | Pre-fills the payment amount |
Payment URL Format
Format:
<Base Payment URL>?accountNumber=<Account Number>&amount=<Amount>
Example:
https://go.payreq.com/pay/tamworth?accountNumber=1234567890&amount=250.75
If the amount is not required, the URL can be created with the account number only:
https://go.payreq.com/pay/tamworth?accountNumber=1234567890
This may be useful where the customer needs to choose the amount themselves, or where the notice supports multiple payment options.
Payment Amount Requirements
The amount value should be supplied as a dollar amount using two decimal places.
Example: amount=100.01
If the amount contains more than two decimal places, the payment page rounds the value to the nearest cent. For example, an amount such as 100.0100001 will be rounded for payment purposes.
Recommended approach:
Input value | Recommended URL value |
$100 | 100.00 |
$100.10 | 100.10 |
$100.015 | 100.02 |
$250.755 | 250.76 |
Where possible, the notice generation process should supply the final amount already rounded to cents.
URL Encoding Requirements
All customer-specific values should be URL encoded before QR code generation.
This is especially important where values may include spaces, ampersands, slashes, apostrophes, or other special characters.
Common examples:
Character | Encoded value |
Space | %20 |
& | %26 |
/ | %2F |
# | %23 |
? | %3F |
For example:
Mr AB Smith & Mrs CD King
Should become:
Mr%20AB%20Smith%20%26%20Mrs%20CD%20King
Example final FastForm URL:
https://test.payreq.com/fastform/demo-biller/create?aN=123456&a1=Mr%20AB%20Smith%20%26%20Mrs%20CD%20King
Payment URLs are usually simpler, as account numbers and payment amounts are typically numeric. However, the values should still be generated safely by the QR code creation process.
Process for Creating QR Codes
1. Confirm the QR Code Use Case
Confirm whether the QR code is intended for:
Use case | Destination |
Digital subscription | Payreq FastForm registration page |
Payment | Payreq payment page |
Each use case should have a clearly labelled QR code so customers understand what action they are taking.
2. Confirm the Base URL
Payreq will confirm the correct biller-specific base URL.
Examples:
https://test.payreq.com/fastform/demo-biller/create
https://test.payreq.com/pay/demo-biller
For production use, the live Payreq URL should be used, not a test URL.
3. Confirm the Required Fields
For a subscription QR code, this may include:
Field | Example |
Account Number / Contact ID | 12345 |
Customer name as shown on the bill | Mr S Smith |
For a payment QR code, this may include:
Field | Example |
Payment reference / BPAY reference number / account number | 1234567890 |
Amount payable | 250.75 |
4. Extract Values from the Notice Data
The mailhouse, print service provider, or composition system should extract the required customer-specific values from the notice data.
For example:
Account Number | Customer Name | Amount |
12345 | Mr S Smith | 250.75 |
5. Encode and Construct the URL
Create the customer-specific URL by adding the relevant query parameters.
Subscription example:
https://test.payreq.com/fastform/demo-biller/create?aN=12345&a1=Mr%20S%20Smith
Payment example:
https://test.payreq.com/pay/demo-biller?accountNumber=1234567890&amount=250.75
6. Generate the QR Code
Generate a QR code from the final customer-specific URL.
Each customer should receive a QR code containing their own unique URL.
7. Test Before Production
Before going live, test a representative sample of QR codes.
Recommended checks:
Check | Expected result |
QR code scans successfully | Customer is taken to the correct Payreq page |
Correct biller page opens | URL uses the correct biller-specific path |
Account/reference number is populated | Correct value appears in the relevant field |
Name is populated, where applicable | Name appears as expected on the FastForm |
Payment amount is populated, where applicable | Amount appears correctly and is rounded to cents |
Special characters work correctly | Names with &, /, apostrophes, or multiple spaces display correctly |
Blank or missing values are handled | Page does not break if an optional value is unavailable |
QR Code Placement Considerations
Where notices include more than one QR code, each code should be clearly separated and labelled.
For example:
QR code | Suggested label |
Payment QR code | Scan to pay this notice |
Digital subscription QR code | Scan to receive future notices digitally |
Avoid placing too many QR codes close together, as this may confuse customers. If a notice already includes a payment QR code, the digital subscription QR code should be placed in a separate section, such as the email notices or digital delivery section.
Notes and Limitations
- The QR code only pre-fills selected fields. The customer must still review the page and complete the required action.
- Only information already available on the customer’s notice should be included in the URL.
- For payment URLs, the amount should be supplied in dollars and cents. Amounts with more than two decimal places will be rounded to the nearest cent.
- For FastForm URLs, the available pre-fill fields may depend on the biller’s FastForm configuration and should be confirmed with Payreq before production.
- Final URL format, field mappings, and QR code samples should be tested and approved before the QR codes are included in a live bill run.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article