Payment failed

Make it fit the send.

• Pass the held items and the charge attempts as lists. A held row renders its print, name, details, quantity and price, and an attempt renders its date and outcome, so a first decline and a fourth read from the same source.
• The automatic retry date is optional: omit it, as the default fixture does, and the email states only how long the slot is held; long-content adds the retry row. Format every amount and date in your application, and send only the last four digits of the card.
• The copy says nothing is cancelled and what happens if the card still does not go through. Edit that sentence to match your own policy. Point the button at the customer's signed-in payment page.
• It is written for Cascara, a fictional coffee roaster that ships on subscription. Replace its mark and the prints with your own, and restyle through the theme tokens in starter.css.

Data this template expects.

{{amountDue}}

Value for amount due.

{{attempts}}

Value for attempts.

{{automaticRetry}}

Value for automatic retry.

{{customerName}}

Value for customer name.

{{declineReason}}

Value for decline reason.

{{grindUrl}}

Link for grind.

{{holdUntil}}

Value for hold until.

{{homeUrl}}

Link for home.

{{items}}

Value for items.

{{nextDelivery}}

Value for next delivery.

{{orderNumber}}

Value for order number.

{{pauseUrl}}

Link for pause.

{{paymentBrand}}

Value for payment brand.

{{paymentLast4}}

Value for payment last 4.

{{roastDate}}

Date for roast.

{{skipUrl}}

Link for skip.

{{updatePaymentUrl}}

Link for update payment.