Could you please add the ability to use per-client fields in the Markdown rendered by the Offline Payment non-merchant gateway module within Blesta ?

... and as I know you like to have a valid use-case for such functionality:

We typically ask our customers to pay us with the following instructions:

"Account Name: Somecompany Ltd

Account Number: 12345678

Account Sort Code: 12-34-56

Please ensure that any payment is sent with a reference of A123A or I1238769I to ensure that payments are allocated properly."

The UK banking system allows for the sender to supply a small amount of alphanumeric text with any payment that can be used by the recipient to determine what the payment was for; the only other things that are seen by the recipient is the sender name (and as you can imagine, there are a lot of people with the same first initial and last name) and the amount paid is usually the same.

A payment reference which starts with 'A' and ends with 'A' is used to indicate which account number (in Blesta terms, the client ID) the payment should be applied to; so, we use our bank's API to get that data and then 'push' the funds into Blesta on the understanding that those funds are used to settle invoices in an oldest first order with excess funds going into the account credit balance; if a client wishes to pay a specific invoice, they can use the payment reference syntax which starts with 'I' and ends with 'I', then our script will use the funds to pay a specific invoice within Blesta and remaining funds are added to the account credit balance.

In order to do this properly with the Offline Payment module, we would ideally like to put things like {client.id} and {invoice.id} in the Markdown, like so:

"Please ensure that any payment is sent with a reference of A{client.id_code}A or I{invoice.id_code}I to ensure that payments are allocated properly."