Accounts generated for collection.
WHAT THEY ARE
Account numbers issued to identify a specific customer, order or purpose.
WHAT THEY SOLVE
Reconciling incoming transfers automatically.
WHY THAT MATTERS
Without them, matching transfers to orders is manual and error-prone.
WHAT THE TYPES ARE
Static: permanently assigned to a customer
Dynamic: generated per transaction, expiring
WHAT STATIC SUITS
Recurring collection from known customers.
WHAT DYNAMIC SUITS
One-off checkout, where the amount is known.
WHAT TO VALIDATE ON RECEIPT
The amount matches what was expected The account maps to the intended purpose The transfer is not a duplicate
WHY AMOUNT VALIDATION MATTERS
Customers send incorrect amounts routinely.
WHAT TO DO ABOUT UNDERPAYMENT AND OVERPAYMENT
Define handling explicitly: partial credit, refund, or hold for instruction.
WHAT TO BUILD
Notification handling, with verification against the provider rather than trusting the message.
WHY
Notifications can be spoofed, and this is a known attack.
WHAT TO ALWAYS DO
Confirm the transaction independently before releasing value.
WHAT TO MONITOR
Unmatched payments, which accumulate and become support load.
