That's definitely an interesting idea. I think instead of a completely different template, it may be a better approach to have different payment tokens that could inject payment-specific details into those other order/receipt e-mail templates. What do you think?

[h][/h]Hi Will

Thank you for your Answer! - Your idea sounds even better 👍.
Just to draw a picture of how the emails differ by type:

[b]Invoice:[/b]
Subject: [[Store.StoreName]] - Invoice for Order [[Order.OrderNumber]]
Body: Thank you for your order [[Order.OrderNumber]]. Please pay the invoice total with the following information (Bank, Account, BIC, IBAN...)

[b]CreditCard:[/b]
Subject: [[Store.StoreName]] - Payment confirmend
Body: Thank you for your Order [[Order.OrderNumber]]

The only problem I see is, that the type of payment can differ within one provider. Say if the customer selects a provider, he can switch between invoice and creditcard during payment. So we would have to change the subject and body tokens according to the payment type selected.

So a subject template like [[Order.Paymenttype.Subject]] Would need multiple definitions accrding to the payment type used.
Subject definition would be
"[[Store.StoreName]] - [h][[Order.Paymenttype.Subject]][/h]"
If the customer pays with credit card this would be substituted with
"[[Store.StoreName]] - [h][[Order.Paymenttype.CreditCard.Subject]][/h]"
This would be substituted with
"[[Store.StoreName]] - [h]Invoice for Order [[Order.OrderNumber]][/h]"
and finally these tokens would be replaced..

Does this make sense?
Reto