When editing your Final Action Email and Dunning Emails, you can use keywords that Advanced Billing will replace dynamically before sending the email. Custom parameters (also known as dynamic variables or liquid variables) are surrounded in double curly braces like this: {{custom_parameter}}
| Parameter | Description |
failure_subject |
The reason the transaction failed. e.g. ‘Failed Credit Card Transaction’, or ‘No Credit Card On File’ depending on whether or not the client has a Credit Card on file. |
from_address |
The “from address” defined for your dunning emails |
name |
The name of your customer. e.g. Bill Williams |
product_price |
The recurring price of the subscription’s current product |
product_name |
The name of the product. e.g. Basic Plan |
balance_in_cents |
The amount, if any, they still owe. e.g. 0 (for $0.00) or 23100 (for $231.00) Useful for conditionally adding a reminder. |
balance |
The amount, if any, they still owe in dollars. e.g. $0.00 or $2.31 |
merchant_name |
Your merchant name. e.g. Acme Corp. |
update_url |
The URL that the customer can use to update their Credit Card information. |
masked_card_number |
The customer’s Credit Card, obscured to only show the last 4 digits.,e.g. XXXX-XXXX-XXXX-1 |
reason_for_decline |
The reason that a transaction was declined at the gateway. |
payment_profile_exists |
This returns true or false depending on whether or not the client, has a Credit Card on file. It can be used to conditionally display text, based on its value. |
Regarding payment_profile_exists, you may use an if statement combined with payment_profile_exists in order to check to see if the payment profile is attached to the subscription.
{% if payment_profile_exists %}
Lorem Ipsum
{% endif %}
For more information on how Dunning works, see our Dunning Overview. For additional information on using dynamic/liquid variables, see Email Templates.
Comments
Article is closed for comments.