How Banks Attach Extra Transaction Details Using Shortened Web Links

A system for banks to send extra payment details, like invoices or receipts, by embedding a short web link inside standard financial transaction messages.

What it covers

This system solves the problem of limited space in traditional bank payment messages. When a transaction occurs, the system stores detailed remittance information (like invoice numbers or line items) on a web server rather than trying to cram it into the payment instruction itself. It then generates a shortened URL pointing to that data and inserts it into the payment message. When the receiving bank or account holder gets the payment, they can click or use that link to retrieve the full, structured details of the transaction.

What it doesn't cover

• —Does not cover the actual movement of funds between bank accounts.
• —Does not cover payment messages that include all remittance data directly within the primary instruction.
• —Does not cover peer-to-peer payment apps that do not use standardized financial credit instructions.
• —Does not cover the physical printing or mailing of paper invoices.

The clever bit

By using a URL as a pointer, the system decouples the payment instruction from the data payload, allowing for unlimited data storage without violating the rigid formatting rules of global payment networks.

Why it matters

Financial messaging standards like ISO 8583 or ACH have strict character limits, making it difficult for businesses to reconcile payments with specific invoices. This patent provides a digital workaround that allows for rich data exchange without needing to overhaul legacy banking infrastructure. It is essential for modernizing B2B payments where automated accounting is required.

Real-world examples

• 1.Corporate B2B payment portals
• 2.Automated accounts receivable software
• 3.Electronic invoice presentment and payment (EIPP) systems