Payment Reference Format Guide
Standardize reference IDs across systems before payments hit reconciliation workflows.
1. Define one canonical reference pattern per payment product.
2. Enforce allowed character sets and maximum length constraints.
3. Preserve case rules consistently between API and exports.
4. Validate checksum rules where local standards require them.
5. Reject ambiguous separators that break parser assumptions.
6. Add format validation before queueing settlement requests.
Implementation notes
Reference format quality directly impacts reconciliation throughput. Keep parser rules centralized and provide deterministic normalization before values reach accounting systems.
Related pages
FAQ
Should references be human-readable? Prefer stable machine-readable format first, then optional human-friendly presentation.
Can one format fit all products? Usually not; keep one canonical format per payment workflow.