This is a list of e-mails that are sent to the customer, the merchant, or both. Some of these messages are sent automatically when events happened which are not configurable within SubscriptionBridge (e.g. a new customer purchases a subscription: you don't control when that happens). Others are sent when certain, “configurable” events happen (e.g. a reminder after a payment failed). These events are configured in the Notification Settings, which are defined at the store level within the SubscriptionBridge Merchant Center.
Scenario: new subscription included a trial period, which is about to expire. The trial may or may not have been free (could have been just a reduced rate), but in any case there is a change in the subscription amount or in the terms of the subscription.
Messages:
(2.a) Sent to Customer: alert message: “N days to go”
(2.b) Sent to Customer: final alert message: “M days to go” (
see example)
… where the number of days (“N” and “M”) is defined in the Notification Settings for the store.
Scenario: new subscription included a trial period, and the trial is stopped before it was scheduled to end. The trial may be stopped directly by the customer (e.g. via the SubscriptionBridge Customer Center) or by the merchant (e.g. customer calls in or sends an email asking for the subscription to be switched to full mode).
Messages:
Scenario: Regular subscription payment, charged successfully. This is not a payment receipt, since SubscriptionBridge is not the payment processor. A separate payment receipt might be sent directly by the payment gateway. This notification is instead a “Subscription Statement” which confirms that payment has been processed and provides other information on the subscription.
Messages:
(4.a) Sent to Customer: Subscription statement following successful payment
(4.b) Sent to Customer: Final subscription statement following last payment occurrence (limited time subscription)
(4.c) Sent to Merchant: Notification of successful payment
Scenario: Regular subscription payment that does not go through successfully. A separate “payment declined” message might be sent directly by the payment gateway. That message, however, does not tell the customer what to do next, unlike the message sent by SubscriptionBridge.
Messages:
Scenario: one or more subscription payments did not go through successfully. Therefore, there was an outstanding balance on the account, which the customer has now paid (e.g. through the SubscriptionBridge Customer Center). There is no notification for unsuccessful payment because the notification is in real time, on the payment page, since this is not an automatic payment.
Messages:
Scenario: one or more subscription payments did not go through successfully. Therefore, there is an outstanding balance on the account. The customer has not paid the balance and a certain number of days have passed (where “P”, “Q”, and “R” - the number of days mentioned below - are defined in the
Notification Settings area of the Merchant Center).
Messages:
(7.a) Sent to Customer: P days have passed since unsuccessful payment
(7.b) Sent to Customer: Q days have passed since unsuccessful payment, final notice
(7.c) Sent to Merchant: notification of 7a
(7.d) Sent to Merchant: notification of 7b
(7.e) Sent to Customer: R days have passed since unsuccessful payment, action taken
(7.f) Sent to Merchant: notification of action taken in 7.e
Scenario: the customer upgraded (different Packages sharing the same Plan), downgraded, added Feature(s), removed Feature(s).
Messages:
(9.a) Sent to Customer: confirmation of change of Package
(9.b) Sent to Customer: confirmation of change of Features
(9.c) Sent to Merchant: notification of change of Package
(9.d) Sent to Merchant: notification of change of Features
Scenario: Merchant adds a feature on behalf of the customer, and there is a balance due for the current billing period (pro-rated amount), or makes a Custom Subscription Change that is associated with a balance due for the current billing period.
Messages:
-
Notifications sent via
Silent Posts
A list of “silent posts” that are posted to the
Callback URL to allow third-party applications to programmatically react to an event.
-
