merchant_guide:notifications_list
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
merchant_guide:notifications_list [2010/03/19 16:50] – matt | merchant_guide:notifications_list [2012/05/24 00:12] (current) – [13. Payment Reminder] matt | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Notifications: | ====== Notifications: | ||
- | ===== 1. Thank You ===== | + | ===== Overview |
- | * Scenario: | + | 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 |
- | * Messages: | + | |
- | * (1.a) Sent to Customer: Trial Exists Message ([[http:// | + | |
- | * (1.b) Sent to Customer: No Trial Message | + | |
- | * (1.c) Sent to Merchant: Notification of new subscription created | + | |
- | ===== 2. Trial To Expire | + | ===== List of e-mails sent ===== |
+ | |||
+ | ==== 1. Confirmation Email ==== | ||
+ | |||
+ | * Scenario: Customer signs up for new product/ | ||
+ | * Messages: | ||
+ | * (1.a) Sent to Customer: Confirmation Message (Trial Period)([[http:// | ||
+ | * (1.b) Sent to Customer: Confirmation Message | ||
+ | * (1.c) Sent to Merchant: New Subscription Message | ||
+ | * (1.d) Sent to Merchant: New Trial Subscription Message | ||
+ | ==== 2. Trial To Expire ==== | ||
* 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. | * 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. | ||
Line 18: | Line 24: | ||
... where the number of days (" | ... where the number of days (" | ||
- | ===== 3. Subscription Status Switched | + | ==== 3. Subscription Status Switched ==== |
* 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). | * 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). | ||
Line 25: | Line 31: | ||
* (3.b) Sent to Merchant: notification of change in subscription status | * (3.b) Sent to Merchant: notification of change in subscription status | ||
- | ===== 4. Transaction | + | ==== 4. Successful |
* 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 " | * 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 " | ||
* Messages: | * Messages: | ||
- | * (4.a) Sent to Customer: | + | * (4.a) Sent to Customer: |
- | * (4.b) Sent to Customer: | + | * (4.b) Sent to Customer: |
- | * (4.c) Sent to Merchant: | + | * (4.c) Sent to Merchant: |
- | + | ==== 5. Unsuccessful Payment | |
- | ===== 5. Transaction NOT Successful ===== | + | |
* Scenario: Regular subscription payment that does not go through successfully. A separate " | * Scenario: Regular subscription payment that does not go through successfully. A separate " | ||
* Messages: | * Messages: | ||
* (5.a) Sent to Customer: Payment NOT OK -> Action to take | * (5.a) Sent to Customer: Payment NOT OK -> Action to take | ||
- | * (5.b) Sent to Merchant: | + | * (5.b) Sent to Merchant: |
- | + | ==== 6. Subscription Balance Paid ==== | |
- | ===== 6. Subscription Balance Paid ===== | + | |
* 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. | * 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. | ||
Line 46: | Line 50: | ||
* (6.a) Sent to Customer: "Thank You" message for Balance Paid. Subscription Account Statement. | * (6.a) Sent to Customer: "Thank You" message for Balance Paid. Subscription Account Statement. | ||
* (6.b) Send to Merchant: notification of successful customer payment against outstanding balance | * (6.b) Send to Merchant: notification of successful customer payment against outstanding balance | ||
+ | ==== 7. Balance Due ==== | ||
- | ===== 7. Subscription Balance Unpaid ===== | + | |
- | + | ||
- | | + | |
* Messages: | * Messages: | ||
* (7.a) Sent to Customer: P days have passed since unsuccessful payment | * (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.b) Sent to Customer: Q days have passed since unsuccessful payment, final notice | ||
- | * (7.c) Sent to Merchant: notification of the issue, in both cases | + | * (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 | ||
- | ===== 8. Subscription Canceled | + | ==== 8. Subscription Canceled ==== |
* Scenario: the subscription has been canceled. There are different reasons for it, which lead to different notifications. | * Scenario: the subscription has been canceled. There are different reasons for it, which lead to different notifications. | ||
* Messages: | * Messages: | ||
* (8.a) Sent to Customer: confirmation of subscription cancellation (customer canceled the subscription) | * (8.a) Sent to Customer: confirmation of subscription cancellation (customer canceled the subscription) | ||
- | * (8.b) Sent to Customer: subscription canceled for non-payment: | + | * (8.b) Sent to Customer: subscription canceled for non-payment: |
* (8.c) Sent to Customer: confirmation of subscription cancellation (merchant canceled the subscription: | * (8.c) Sent to Customer: confirmation of subscription cancellation (merchant canceled the subscription: | ||
* (8.d) Sent to Merchant: notification of subscription cancellation (sent in scenario 8.a & 8.b, not needed for 8.c since the cancellation was triggered by the merchant) | * (8.d) Sent to Merchant: notification of subscription cancellation (sent in scenario 8.a & 8.b, not needed for 8.c since the cancellation was triggered by the merchant) | ||
- | ===== 9. Subscription Changed | + | ==== 9. Subscription Changed ==== |
* Scenario: the customer upgraded (different Packages sharing the same Plan), downgraded, added Feature(s), removed Feature(s). | * Scenario: the customer upgraded (different Packages sharing the same Plan), downgraded, added Feature(s), removed Feature(s). | ||
Line 70: | Line 76: | ||
* (9.a) Sent to Customer: confirmation of change of Package | * (9.a) Sent to Customer: confirmation of change of Package | ||
* (9.b) Sent to Customer: confirmation of change of Features | * (9.b) Sent to Customer: confirmation of change of Features | ||
- | * (9.c) Sent to Merchant: notification of subscription changes | + | * (9.c) Sent to Merchant: notification of change of Package |
+ | * (9.d) Sent to Merchant: notification of change of Features | ||
- | ===== 10. New Balance | + | ==== 10. New Balance ==== |
* 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. | * 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. | ||
Line 79: | Line 86: | ||
* (10.a) Sent to Customer: Notification of New Balance | * (10.a) Sent to Customer: Notification of New Balance | ||
- | ===== 11. Credit Card Expiring | + | ==== 11. Credit Card Expiring ==== |
* Scenario: The system detects that the credit card expiration date is before the next payment date. | * Scenario: The system detects that the credit card expiration date is before the next payment date. | ||
Line 85: | Line 92: | ||
* (11.a) Sent to Customer: Notification of expiring credit card | * (11.a) Sent to Customer: Notification of expiring credit card | ||
* (11.b) Sent to Customer: Notification credit card has expired | * (11.b) Sent to Customer: Notification credit card has expired | ||
+ | |||
+ | ==== 12. ==== | ||
+ | |||
+ | ==== 13. Reminders ==== | ||
+ | |||
+ | * Scenario: The system detects that the next payment date is approaching and sends the customer a reminder. This is useful with long subscription periods in which the customer may forget they are still subscribed. It also helps reduce chargebacks. | ||
+ | * Messages: | ||
+ | * (13.a) Sent to Customer: Notification of upcoming payment | ||
+ | * (13.b) Sent to Customer: Notification of upcoming renewal | ||
+ | |||
+ | |||
+ | ===== Related articles ===== | ||
+ | |||
+ | * [[merchant_guide: | ||
+ | * Notifications sent via [[merchant_guide: | ||
+ | * [[developer_guide: |
merchant_guide/notifications_list.1269031835.txt.gz · Last modified: 2010/03/19 00:00 (external edit)