Maqetin emails subscribers whose renewal payment failed.
A renewal is declined and the subscriber has not been told. Maqetin reads the failure and any later payment in your app’s events, and asks the card to be updated if no payment went through.
Sample scene: a news subscription app in London.
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.
A failed payment is about the account.
It names the card by its last four digits and links to the page that updates it.
- Print the card. Send the last four digits with payment.failed, and the email can print them. The full number has no place in an event.
- Stop when the payment goes through. The journey looks for payment.succeeded since the person entered, so a retry that works within the hour means no email.
- Choose the path. A journey email skips people who opted out of marketing. A notice sent through the send API reaches them.
Hi Jane,
We could not renew your subscription with the card ending 4417. Update it in one step and nothing changes.
Update your cardEvents to send.
Your server sends each one when your billing system reports it. The journey above uses the first two.
- payment.failed
- A renewal charge is declined.
- payment.succeeded
- A charge goes through.
- subscription.started
- A person subscribes.
- subscription.cancelled
- A subscriber cancels.
A template that fits.
Start with the renewals that fail.
Book a demo and we'll show you Maqetin on payment journeys like yours.