Merge Tags

Dany Bouchard
Dany Bouchard
  • Updated

Overview

A merge tag is essentially a placeholder in your message template that gets replaced with real data when the message is sent out.

For instance, using a merge tag like {{entity.firstName}} in your template will automatically insert the recipient's actual first name into each communication.

Guide: Customer communication

This article is part of a larger guide going over the concept of customer communication

Using merge tags

Some tags can be used across all system messages and custom communication, they are known as common tags, while system tags are limited to specific templates.
Learn more below.

To insert a merge tag inside a communication template, you can either type it out manually, or use the merge tag menu located inside the text toolbar. The toolbar appears when you edit a text element.

Using the merge tag menu is usually much easier and safer, since you will be provided a list of all the available tags for the current template.

merge_tags_button.png

Additionally, some tags have sub-elements you can access using the dot notation, like so: {{account.firstName}}.

Use the merge tag insertion menu described above to discover sub-elements linked to a merge tag.

 

Common tags

Common tags are available across all templates.

Category Merge tag Description
entity {{entity.activationDate}}

The date the services were activated on the account.

This comes formatted as: YYYY-MM-DD. To change it to a MM/DD/YYYY format adjust the merge tag to the following: {{entity.activationDate | shortDate}}

Available on accounts and commercial accounts only.
entity {{entity.autoPaymentEnabled}}

Returns a true/false value indicating whether automatic payments are enabled on the account. This tag is meant to be used as a condition to display or hide copy within a template rather than printed on its own.

Available on accounts, commercial accounts and property groups.
entity {{entity.billingAddress}}

The full billing address associated with the account. For example: 123 Fake Street, Toronto, ON L6H 1Y4. This is the "Physical Address" where the services are being provided at.

 

It is broken down into multiple different tags:

  • {{entity.billingAddress.buildingName}} -> (If applicable) The name of the building at the address
  • {{entity.billingAddress.country}} -> The country associated with the address. Always shown as the 3-digit short form. For example, CAN for Canada or USA for the United States.
  • {{entity.billingAddress.county}} -> (If applicable) The name of the county the address falls under
  • {{entity.billingAddress.line1}} -> The full address line (i.e. 123 Fake Street)
  • {{entity.billingAddress.line2}} -> (If applicable) The second line of the address
  • {{entity.billingAddress.locality}} -> The city the address is located in
  • {{entity.billingAddress.postalCode}} -> The postal or zip code of the address
  • {{entity.billingAddress.premise}} -> The number in the address line
  • {{entity.billingAddress.region}} -> The state/province
  • {{entity.billingAddress.subBuilding}} -> If the account resides in an apartment or where there is more than one residence at an address, this can be used. For example, in the "15-123 Fake Street" or "123 Fake Street APT 15", "15" would be the subbuilding.
  • {{entity.billingAddress.throughfare}} -> The name of the street in the address line
entity {{entity.clientPortalCreationLink}}

The unique link inviting the customer to create their client portal account. Use this in welcome and onboarding communications.

Available on accounts, commercial accounts and property group managers.
entity/clientPortalUser {{entity.clientPortalUser.username}} The username of the customer's existing client portal user. This comes back empty when the customer has not created a client portal account yet, which makes it useful as a condition alongside clientPortalCreationLink.
entity {{entity.firstName}} Display the first name on the account.
entity {{entity.gaiiaId}} The unique gaiia ID assigned to each account.
entity {{entity.id}} The account's UUID. This is the long identifier used in the account URL, not the Account ID. Also available on commercial accounts, property groups and property group managers.
entity {{entity.internetProvider}} Name of the internet provider assigned to each account.
entity {{entity.lastName}} Display the last name on the account.
entity {{entity.mailingAddress}}

If the account receives mail at an alternate address these merge tags can be used. This comes from the "Mailing Address" fields of the account.

It is broken down into multiple different tags:

  • {{entity.mailingAddress.buildingName}} -> (If applicable) The name of the building at the address
  • {{entity.mailingAddress.country}} -> The country associated with the address. Always shown as the 3-digit short form. For example, CAN for Canada or USA for the United States.
  • {{entity.mailingAddress.county}} -> (If applicable) The name of the county the address falls under
  • {{entity.mailingAddress.line1}} -> The full address line (i.e. 123 Fake Street)
  • {{entity.mailingAddress.line2}} -> (If applicable) The second line of the address
  • {{entity.mailingAddress.locality}} -> The city the address is located in
  • {{entity.mailingAddress.postalCode}} -> The postal or zip code of the address
  • {{entity.mailingAddress.premise}} -> The number in the address line
  • {{entity.mailingAddress.region}} -> The state/province
  • {{entity.mailingAddress.subBuilding}} -> If the account resides in an apartment or where there is more than one residence at an address, this can be used. For example, in the "15-123 Fake Street" or "123 Fake Street APT 15", "15" would be the subbuilding.
  • {{entity.mailingAddress.throughfare}} -> The name of the street in the address line
entity {{entity.name}} If a value has been provided in the "Account name" field of account this merge tag can be used. This is often done if billing commercial customers who have a business name that needs to be tracked. 
entity {{entity.primaryEmail}} Display the primary email on the account.
entity {{entity.primaryHomePhone}} The home phone number captured on the account.
entity {{entity.primaryMobilePhone}} The mobile phone number captured on the account.
entity {{entity.primaryWorkPhone}} The work phone number captured on the account.
entity {{entity.referralCode}} The unique referral code associated with the account.
entity {{entity.tags}}

The list of tags applied to the account. Each entry is broken down into multiple different tags:

  • {{ tag.definition.key }} -> The key of the tag definition, for example loyaltyTier
  • {{ tag.value }} -> The value stored on the account for that tag
  • {{ tag.id }} -> The unique identifier of the tag on the account

Because an account can carry several tags, this one has to be used inside a loop. See the "Working with lists" section below.

Available on accounts, commercial accounts and property groups.
admin {{admin.primaryClientPortalLink}} The full URL of your client portal.
billing {{billing.availableFunds}}

If the account has any credits on the account, this merge field can be used to show it.

 

Please note, this merge tag comes unformatted with the currency to allow for the creation of conditional logic based on an amount.

 

If displaying this just as a value, the following can be done to format it as a currency: {{billing.availableFunds | currency}}
billing {{billing.balanceDue}}

The current balance due of the account. This only includes outstanding balances on invoiced items.

Please note, this merge tag comes unformatted with the currency to allow for the creation of conditional logic based on an amount.

 

If displaying this just as a value, the following can be done to format it as a currency: {{billing.balanceDue | currency}} 
billing {{billing.currency}}

The billing currency of the account, shown as a three-letter code such as USD or CAD.

You do not need to add this tag to format amounts. The currency filter already applies the account's currency on its own.
billing/lastInvoice {{billing.lastInvoice.dueDate}}

The current due date of the current invoice sent out to the account. This is usually the invoice sent for the current billing period.

 

This comes formatted as: YYYY-MM-DD. To change it to a MM/DD/YYYY format adjust the merge tag to the following: {{billing.lastInvoice.dueDate | shortDate}} 
billing/period {{billing.lastInvoice.period.end}}

The end date of the current billing period of the account.

This comes formatted as: YYYY-MM-DD. To change it to a MM/DD/YYYY format adjust the merge tag to the following:

{{billing.lastInvoice.period.end | shortDate}}
billing/period {{billing.lastInvoice.period.start}}

The start date of the current billing period of the account.

This comes formatted as: YYYY-MM-DD. To change it to a MM/DD/YYYY format adjust the merge tag to the following:

{{billing.lastInvoice.period.start | shortDate}}
billing {{billing.subscriptions}} The list of active subscriptions on the account, including the price paid, the standard product price and the product name. Because an account can carry several subscriptions, this one has to be used inside a loop. See the "Subscription tags" section below for the full breakdown and examples.
billing {{billing.totalBalance}}

The overall balance of the account including both invoiced and uninvoiced transactions.

 

Please note, this merge tag comes unformatted with the currency to allow for the creation of conditional logic based on an amount.

 

If displaying this just as a value, the following can be done to format it as a currency: {{billing.totalBalance | currency}}
branding/assets {{branding.assets.logoImageUrl}}

The URL of your organization's logo, as configured in your branding settings. Use it as the source of an image element: <img src="{{branding.assets.logoImageUrl}}">

This is the only supported logo tag. A tag such as {{tenant_logo}} does not exist and renders as an empty image.
branding/theme/colors {{branding.theme.colors.actionPrimaryDefault}} Your organization's primary action color, as configured in your branding settings. Useful for styling buttons so that communications follow your brand.
branding/theme/colors {{branding.theme.colors.backgroundSecondary}} Your organization's secondary background color, as configured in your branding settings.

Subscription tags

The billing.subscriptions tag exposes the account's active subscriptions, which lets a communication show what the customer pays, what the standard price is, and how much they save.

Only subscriptions that are owned by the account, assigned, and not suspended are included.

Prices come from these tags unformatted and in cents. Always pass them through the currency filter to display them, for example {{ sub.priceDisplay | currency }}.

The order of the subscriptions is not guaranteed. Referring to a fixed position such as billing.subscriptions.0 can land on a different product from one account to the next, so use a loop with a condition instead.

Merge tag Description
{{ sub.priceDisplay }} The price the account actually pays for the subscription. This is the price override when one is set on the subscription, and the standard product price otherwise. This is the tag to use whenever you display a price to a customer.
{{ sub.version.price }} The standard price of the product version, before any override. Use it alongside priceDisplay to show a customer the difference between the standard price and what they pay.
{{ sub.priceOverrideInCents }} The custom price set on the subscription, when there is one. This comes back empty when the subscription is billed at the standard price, which makes it useful as a condition.
{{ sub.version.product.name }} The name of the product, as it appears on invoices and in the client portal.
{{ sub.version.product.type }} The type of the product, shown as "DEBIT", "CREDIT" or "DISCOUNT".
{{ sub.version.currency }} The currency of the subscription, shown as a three-letter code such as USD.
{{ sub.numberOfRecurrences }} The total number of times the product is billed, when the product is configured with a limited number of recurrences.
{{ sub.remainingNumberOfRecurrences }} How many billing cycles are left on a subscription with a limited number of recurrences. Useful for messages such as a promotion ending soon.
{{ sub.numberOfRecurrenceDelay }} The number of billing cycles to wait before the subscription starts being billed.
{{ sub.metadata }} / {{ sub.metadataEntries }} Any custom fields stored on the subscription. Use metadata.yourFieldKey.value to display one field, or loop over metadataEntries to display them all.
{{ sub.items }} The individual items making up the subscription, each with their own metadata and metadataEntries.

Example: showing a discounted price and the savings

This example loops over the subscriptions, keeps only the product whose name contains "Internet", and prints the price paid, the standard price, and the resulting savings per month and per year.

{% for sub in billing.subscriptions %}
{% if sub.version.product.name contains "Internet" %}
Your new price: {{ sub.priceDisplay | currency }} / month
Our standard price for the same package: {{ sub.version.price | currency }} / month
You are saving: {{ sub.version.price | minus: sub.priceDisplay | currency }} every month ({{ sub.version.price | minus: sub.priceDisplay | times: 12 | currency }} every year)
{% endif %}
{% endfor %}

Replace the text inside the condition with whatever identifies the product you want to display.

Do not use the Send test button to check these values. Test sends render sample placeholder data rather than the real account, so the prices shown will not match the account. Send a real communication to a test account instead.

Working with lists

Most merge tags return a single value, but billing.subscriptions, entity.tags and subscription items return a list. Lists have to be looped over, using the same syntax as conditional logic.

{% for tag in entity.tags %}
{{ tag.definition.key }}: {{ tag.value }}
{% endfor %}

You can also filter a list down to a single entry with a condition inside the loop, as shown in the subscription example above.

Formatting filters

Filters change how a value is displayed. They are added after the tag with a pipe character, and several can be chained together.

Filter Description Example
currency Formats an amount stored in cents as a currency, using the account's billing currency and language. {{billing.balanceDue | currency}}
shortDate Formats a date as MM/DD/YYYY rather than YYYY-MM-DD. {{billing.lastInvoice.dueDate | shortDate}}
localDate Formats a date and time, with an optional format and time zone. The default format is YYYY/MM/DD HH:mm. {{someDate | localDate: "YYYY/MM/DD", "America/Toronto"}}
phoneNumber Formats a phone number for display. {{entity.primaryMobilePhone | phoneNumber}}
duration Formats a number of seconds as a duration. {{someDuration | duration}}
paymentMethod Formats a payment method as its type, brand and last digits. {{somePaymentMethod | paymentMethod}}
minus, plus, times, divided_by Standard math filters. Useful for calculating a difference between two amounts or projecting a monthly amount over a year. Apply the currency filter last. {{ sub.version.price | minus: sub.priceDisplay | times: 12 | currency }}

System tags

System tags are bound to specific templates and cannot be used outside of them. They are listed below by template, which is what you need when you are editing a specific message. Every tag shown is available on that template, in addition to the common tags.

Some templates listed below might not be configured on your instance of gaiia. This list is for reference only.

Scroll right to view the whole table on smaller screens.

A. Activation, appointments and service changes

Template Merge tags
Activation appointment necessary
Installation appointment confirmed
Installation appointment reminder
Appointment modification completion
Move appointment confirmation
Outlet relocation appointment confirmation
Troubleshooting appointment confirmation		 {{customerName}}, {{installationDate}}, {{earliestInstallationTime}}, {{latestInstallationTime}}
Activation no appointment necessary {{customerName}}, {{transferDate}}
Activation convert to transfer {{customerName}}, {{transferDate}}, {{latestDisconnectionSubmissionDate}}, {{provider}}
Transfer activation initial {{customerName}}, {{previousProviderDeactivationDate}}, {{previousProviderDeactivationDays}}
Transfer activation warning {{customerName}}, {{tpiaDeactivationDate}}
Transfer activation failed
No tech activation initial
With tech activation initial
Services activated
Invalid previous account name
Appointment completed
Appointment missed
Appointment delayed
Speed modification completion
Outlet relocation completion
Modem modification completion
Modem sent contact us notice
Moving in no disconnection warning
Password changed		 {{customerName}}
Open access network activation initial {{customerFirstName}}, {{customerLastName}}
Move no technician request notice {{customerName}}, {{activationDate}}
Service cancellation without equipment {{customerName}}, {{cancellationCategory}}, {{cancellationReason}}, {{hasPhoneService}}
Service cancellation with equipment {{customerName}}, {{accountGaiiaId}}, {{cancellationCategory}}, {{cancellationReason}}, {{hasPhoneService}}
Seasonal suspension {{customerName}}, {{suspensionDate}}, {{maxReactivationDate}}, {{maxSuspensionDurationInMonths}}
Reactivation {{customerName}}, {{currency}}, and a {{subscriptions}} list where each entry has {{ sub.name }}, {{ sub.price }}, {{ sub.currency }}
Phone portability confirmed {{customerName}}, {{portingActivationDate}}
New phone number completed {{customerName}}, {{newPhoneNumber}}

B. Shipments and equipment

Template Merge tags
Sent shipment {{customerName}}, {{carrier}}, {{trackingPin}}, {{shippingAddress}}
Return shipment created {{customerName}}, {{accountId}}, {{dueDate}}, and a {{formattedEquipments}} list of equipment names
Return shipment completed {{customerName}}, and a {{formattedEquipments}} list of equipment names
Return shipment first reminder
Return shipment second reminder		 {{customerName}}, {{dueDate}}, {{currency}}, and an {{equipmentWithPrices}} list where each entry has {{ item.name }}, {{ item.price }}, {{ item.quantity }}

C. Contracts, referrals and account access

Template Merge tags
Pending contract signature initial
Contract signed confirmation
Contract removed		 {{customerName}}, {{contractName}}
Pending contract signature reminder {{customerName}}, and a {{pendingContractNames}} list of contract names
Client portal creation link {{customerName}}, {{creationLink}}, {{accountGaiiaId}}, {{accountCreatedDate}}, {{tenantName}}
Verification pin {{customerName}}, {{pin}}
Cognito confirmation code {{confirmationCode}}, {{triggerSource}}
Referral {{refererFirstName}}, {{refererLastName}}, {{refereeFirstName}}, {{refereeLastName}}, {{referralCode}}
Referral subscribed {{refererFirstName}}, {{refererLastName}}, {{refereeFirstName}}, {{refereeLastName}}
Personal information updated {{firstName}}, {{lastName}}, {{email}}, {{homePhone}}, {{mobilePhone}}, {{workPhone}}, {{role}}, {{emailLastVerifiedAt}}, {{mobilePhoneLastVerifiedAt}}. Each one is present only when that field actually changed, which makes them useful as conditions.

D. Ordering

Template Merge tags
Initial order confirmation {{firstName}}, {{accountGaiiaId}}, {{accountCreatedDate}}, {{clientPortalCreationLink}}, {{physicalAddress}}, {{mailingAddress}}, {{provider}}, {{activationType}}, {{transferDate}}, {{transferDeadlineDate}}, {{supportLink}}, {{isPortingNumber}}, {{isReceivingNewNumber}}, {{needsCoaxialCable}}, {{isOutletInstallationRequired}}, {{ property.name }}, {{ property.billingManagement }}, and an {{appointments}} list where each entry has {{ appointment.day }}, {{ appointment.timeSlot.timeOne }}, {{ appointment.timeSlot.timeTwo }}

E. Billing and payments

Amounts on these templates come through unformatted and in cents, so that they can be used in conditions. Pass them through the currency filter to display them.

Template Merge tags
Statement {{invoiceNumber}}, {{amountRemaining}}, {{currency}}, and a {{lastPayment}} object (see below). {{amountRemaining}} is present only when a balance is left on the invoice.
Manual statement {{invoiceNumber}}, {{amountRemaining}}, {{totalBalanceDue}}, {{availableFunds}}, {{currency}}, and a {{lastPayment}} object (see below)
Payment due {{amountRemaining}}, {{totalBalanceDue}}, {{dueInDays}}, {{currency}}
Overdue {{amountRemaining}}, {{totalBalanceDue}}, {{currency}}
Final notice before delinquency {{amountRemaining}}, {{totalBalanceDue}}, {{currency}}
Delinquent - Overdue payment notice {{totalAmountDue}}, {{paymentAmount}}, {{numberOfDaysNotice}}, {{paymentArrangementLimitISODate}}, {{currency}}
Delinquent - Payment arrangement {{currency}}, and an {{arrangement}} list where each entry has {{ item.totalAmount }} and {{ item.dueISODate }}. The list holds at most ten entries.
Delinquent - Suspension of services notice {{totalAmountDue}}, {{contactCustomerCareLimitISODate}}, {{currency}}
Delinquent - Suspension of services within 24 hours notice {{totalAmountDue}}, {{suspensionISODate}}, {{suspensionHours}}, {{currency}}
Payment successful {{ transaction.amount }}, {{ transaction.feeAmount }}, {{ transaction.currency }}, and a {{paymentMethod}} object (see below)
Payment failed {{amountDue}}, {{ transaction.amount }}, {{ transaction.currency }}, {{currency}}, and a {{paymentMethod}} object (see below)
Retry payment failed {{totalAmountDue}}, {{currency}}, {{daysBetweenNextAttempt}}, {{maxAttemptNumberReached}}, and a {{lastPayment}} object (see below). Exactly one of {{daysBetweenNextAttempt}} and {{maxAttemptNumberReached}} is present, depending on whether more retries remain, so both work as conditions.
Credit card expiring a {{paymentMethod}} object (see below)
Credit card payment method created {{ creditCard.brand }}, {{ creditCard.maskedIdentificationNumber }}, {{ creditCard.status }}
Bank account payment method created {{ bankAccount.maskedIdentificationNumber }}, {{ bankAccount.status }}
Credit card payment method deleted {{ creditCard.brand }}, {{ creditCard.maskedIdentificationNumber }}. Unlike the created message, this one carries no {{ creditCard.status }}.
Bank account payment method deleted {{ bankAccount.maskedIdentificationNumber }}. Unlike the created message, this one carries no {{ bankAccount.status }}.
Bank account verification {{ bankAccount.last4 }}, {{ bankAccount.holderName }}, {{ stripe.arrivalDate }}, {{ stripe.hostedVerificationURL }}, {{ stripe.microDepositType }}
Mandate setup invitation {{ mandateSetup.url }}

The payment method and last payment objects

Several billing templates share the same two objects.

Merge tag Description
{{ paymentMethod.type }} The kind of payment method, shown as "CREDIT_CARD" or "BANK_ACCOUNT".
{{ paymentMethod.brand }} The card brand, for credit cards.
{{ paymentMethod.maskedIdentificationNumber }} The last digits of the card or bank account.
{{paymentMethod | paymentMethod}} Formats the whole object as a readable label, combining the type, the brand and the last digits. Use this rather than assembling the three tags above by hand.
{{ lastPayment.amount }} The amount of the most recent payment, in cents.
{{ lastPayment.feeAmount }} Any fee charged on that payment, in cents.
{{ lastPayment.status }} The status of that payment.
{{ lastPayment.failureCode }} Why the payment failed. Present only on a failed payment, so it works as a condition.
{{ lastPayment.paymentMethod }} The payment method used, with the same sub-tags as {{paymentMethod}} above.

F. Work orders and technicians

Template Merge tags
Technician on the way {{ tenant.name }}, {{ technician.name }}, {{ account.name }}, {{ workOrder.locationName }}, {{ workOrder.appointmentDisplayMode }}, {{ workOrder.arrivalWindowStartDate }}, {{ workOrder.arrivalWindowEndDate }}, {{estimatedTravelTimeInMinutes}}, {{estimatedTimeArrival}}
Work order auto assigned {{ tenant.name }}, {{ workOrder.date }}, {{ workOrder.startTime }}, {{ workOrder.endTime }}, {{ workOrder.preferredTimeSlotStartTime }}, {{ workOrder.preferredTimeSlotEndTime }}, {{ workOrder.locationName }}, {{ workOrder.appointmentDisplayMode }}, {{ workOrder.arrivalWindowStartDate }}, {{ workOrder.arrivalWindowEndDate }}
Work order assigned to account {{ tenant.name }}, {{ workOrder.date }}, {{ workOrder.startTime }}, {{ workOrder.endTime }}, {{ workOrder.locationName }}, {{ workOrder.appointmentDisplayMode }}, {{ workOrder.arrivalWindowStartDate }}, {{ workOrder.arrivalWindowEndDate }}

The arrival window tags are present only when an arrival window is set on the work order. {{ workOrder.appointmentDisplayMode }} is always present and tells you which of the exact time and the arrival window your organization displays, which makes it useful as a condition.

G. Tickets

Template Merge tags
External ticket created {{subject}}, {{ tenant.id }}, {{ tenant.name }}, {{ tenant.slug }}, {{ mailbox.name }}, {{ mailbox.replyEmailAddress }}, {{ ticket.id }}, {{ ticket.readableId }}, {{ ticket.title }}, {{ ticket.description }}, {{ ticket.createdAt }}, {{ comment.id }}, {{ comment.type }}, {{ comment.message }}, {{ comment.createdBy }}, {{ comment.createdAt }}
Ticket new external comment The same tags as above, minus {{ comment.id }} and {{ comment.type }}, plus {{ fromUser.firstName }}, {{ fromUser.lastName }}, {{ fromUser.email }} for the agent who replied

Replaced system tags

The tags on the left still work today, but they are no longer maintained and they arrive already formatted, which means you cannot use them in a condition or change how they are displayed. Use the replacement on the right instead.

Old tag Use instead Templates
{{amountDue}} {{amountRemaining | currency}} Statement, Manual statement, Payment due, Overdue
{{amountDue}} {{totalAmountDue | currency}} Delinquent - Overdue payment notice, Delinquent - Suspension of services notice, Delinquent - Suspension of services within 24 hours notice, Retry payment failed
{{totalAmountDue}} {{amountDue | currency}} Payment failed only. Note that this template uses the two names the other way around from the rest of billing, so check which template you are editing.
{{minimumPaymentAmount}} {{paymentAmount | currency}} Delinquent - Overdue payment notice
{{paymentArrangementLimitDate}} {{paymentArrangementLimitISODate | shortDate}} Delinquent - Overdue payment notice
{{contactCustomerCareLimitDate}} {{contactCustomerCareLimitISODate | shortDate}} Delinquent - Suspension of services notice
{{suspensionDate}} {{suspensionISODate | shortDate}} Delinquent - Suspension of services within 24 hours notice. The Seasonal suspension template keeps {{suspensionDate}}.
{{ arrangement.0.amount }} {{ arrangement.0.totalAmount | currency }} Delinquent - Payment arrangement
{{ arrangement.0.dueDate }} {{ arrangement.0.dueISODate | shortDate }} Delinquent - Payment arrangement
{{ lastPayment.formattedAmount }} {{ lastPayment.amount | currency }} Statement, Retry payment failed
{{ lastPayment.paymentMethodName }} {{ lastPayment.paymentMethod | paymentMethod }} Statement, Retry payment failed
{{ paymentMethod.name }} {{ paymentMethod | paymentMethod }} Credit card expiring, Payment successful, Payment failed
{{ transaction.formattedAmount }} {{ transaction.amount | currency }} Payment successful, Payment failed

Related to

Was this article helpful?

Have more questions? Submit a request