Configure Payment QR code settings
Enable or disable QR output, set PDF coordinates and configure legacy content for payment PDFs. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Setup → Settings → QR Code Compliance → Payments
Before you start
- Use an authorised account and confirm the source CRM record or setting is correct.
- Follow the exact route shown above; do not force database values to imitate a completed action.
What you’ll accomplish
Enable or disable QR output, set PDF coordinates and configure legacy content for payment PDFs. These instructions follow the supplied module’s live hooks, controller, model, view and validation flow.
Follow these steps
- Set Show Payment QR Code to Yes or No.
- Enter both Payment QR X and Y coordinates for manual placement, or leave a coordinate blank to use the automatic current PDF position.
- When compliance is disabled, review the legacy Payment QR content and merge fields.
- Save and generate a test PDF.
Fields and options to review
Action scopeEnable or disable QR output, set PDF coordinates and configure legacy content for payment PDFs.
Module version2.1.0
NavigationAdmin Area → Setup → Settings → QR Code Compliance → Payments
EvidenceVerify the stored record, status, output, email, event or log produced by the code path.
Rules the system enforces
- The supplied default is disabled.
- When compliance is enabled, QR content is the secure public signing URL rather than the legacy merge-field textarea.
How to confirm it worked
- The requested record, output or setting is created or updated through the supported module flow.
- Any related status, count, email, audit/event, PDF/file or queue evidence agrees with the source action.
- An error message is investigated rather than bypassed.
Security, privacy and operational checks
- Apply least privilege and verify the correct customer, lead, sales document or recipient before processing.
- Protect public tokens, recipient data, IP/browser evidence, templates and exported files according to organisational policy.
- Test configuration changes with controlled records before production-wide use.
- Retain or delete evidence only under an authorised retention process.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.