Notification messages support twelve default template tags to provide information to your purchasers and administrators. You can add additional notification messages by using the My Tickets custom field api.

The content produced by some of these tags is simple strings, but others produce more complicated data. All of the tags automatically toggle their formats depending on whether you’re sending HTML or plaintext email.

{receipt}
A link to the user’s receipt.
{tickets}
For e-tickets or printable tickets, a list of the purchased tickets.
{name}
The purchaser’s name, as provided in the shopping cart.
{blogname}
The name of your site.
{key}
The purchase’s internal payment ID. (Probably only useful for admin messages!)
{purchase}
Purchase data: tickets purchased, how many, at what price.
{address}
The purchaser’s provided shipping address.
{transaction}
All transaction data from the payment gateway.
{transaction_id}
The payment gateway’s transaction ID.
{amount_due}
For offline payments, the amount owed on the purchase.
{method}
The ticketing method chosen by the purchaser.

In general, I recommended that you at minimum provide your purchaser’s with their receipt link and their purchase data, regardless of the ticketing and payment methods you allow.