Maqetin emails the customer whose renewal payment failed.
For a customer whose card was declined at renewal. It makes updating the card one step. A journey sends it an hour after the failure, unless a payment has gone through.
The email.
A sample to adapt: change the names, the product and the button to yours.
FromShelfwise <hello@mail.shelfwise.app>SubjectYour payment did not go throughPreviewUpdate your card to keep your shops running.
Hi Sarah,
We could not renew your Shelfwise plan with the card ending 4417. Update it in one step and nothing changes.
Update your cardShelfwise, Austin
Sample workspace: Shelfwise, stock and invoicing software for independent shops, based in Austin.
How it is sent.
The journey starts when your app sends payment.failed. It waits 1 hour, then checks whether payment.succeeded arrived since the person entered. If it did, they leave and no email goes. If not, the email goes.
Trigger
Payment failed
payment.failed
Wait
Wait 1 hour
Condition
Paid since?
payment.succeededsince entering
Yes
Exit
Exit
No
Send email
Send the card update
Exit
Exit
Events to send.
Your app sends two events for the same person.
- payment.failed
- Starts the journey. Send card_last4 with it, and the email can print the last four digits.
- payment.succeeded
- Ends the journey early. A retry that goes through within the hour means no email.
Check before you send.
- Decide who must receive it. A journey email skips people who opted out of marketing. If every customer must get this notice, send it from your server through the send API instead.
- Keep card details out of the email. Print the last four digits at most.
- Set the wait to your retry schedule. A wait can be any length from 5 seconds to a year. One hour is only the sample.