SubscriptionBridge: recurring billing and subscription management system - Documentation

User Tools

Site Tools

You are here: SubscriptionBridge Documentation » Merchant User Guide » Notifications: List of E-mail Messages Sent
Trace:
merchant_guide:notifications_list

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
merchant_guide:notifications_list [2010/04/12 14:26] – earlyimpactmerchant_guide:notifications_list [2012/05/24 00:12] (current) – [13. Payment Reminder] matt
Line 7: Line 7:
 ===== List of e-mails sent ===== ===== List of e-mails sent =====
  
-==== 1. Thank You ====+==== 1. Confirmation Email ====
  
-  * Scenario: customer signs up for new product/service and a new subscription is created in SubscriptionBridge. There may or may not be a trial period.+  * Scenario: Customer signs up for new product/service and a new subscription is created in SubscriptionBridge. There may or may not be a trial period.
   * Messages:   * Messages:
-    * (1.a) Sent to Customer: Trial Exists Message ([[http://www.earlyimpact.com/images/2009/sb_notification_trialAccount.gif|see example]]) +    * (1.a) Sent to Customer: Confirmation Message (Trial Period)([[http://www.earlyimpact.com/images/2009/sb_notification_trialAccount.gif|see example]]) 
-    * (1.b) Sent to Customer: No Trial Message +    * (1.b) Sent to Customer: Confirmation Message 
-    * (1.c) Sent to Merchant: Notification of new subscription created +    * (1.c) Sent to Merchant: New Subscription Message 
 +    * (1.d) Sent to Merchant: New Trial Subscription Message
 ==== 2. Trial To Expire ==== ==== 2. Trial To Expire ====
  
Line 31: 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 Successful ====+==== 4. Successful Payment ====
  
   * 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.   * 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:   * Messages:
-    * (4.a) Sent to Customer: subscription statement following successful payment +    * (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.b) Sent to Customer: Final subscription statement following last payment occurrence (limited time subscription) 
-    * (4.c) Sent to Merchant: notification of successful payment +    * (4.c) Sent to Merchant: Notification of successful payment 
- +==== 5. Unsuccessful Payment ====
-==== 5. Transaction NOT Successful ====+
  
   * 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.   * 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:   * 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: notification of unsuccessful payment +    * (5.b) Sent to Merchant: Unsuccessful payment message
 ==== 6. Subscription Balance Paid ==== ==== 6. Subscription Balance Paid ====
  
Line 52: 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 ==== +  * 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 [[merchant_guide:notifications|Notification Settings]] area of the Merchant Center).
- +
-  * 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" and "Q" - the number of days mentioned below - are defined in the [[merchant_guide:notifications|Notification Settings]] area of the Merchant Center).+
   * 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 ====
Line 66: Line 66:
   * 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: sent R days after 7.b is sent (where "R" is the number of days after which a subscription is cancelled for non-payment, which is set in the [[merchant_guide:notifications|Notification Settings]] area of the Merchant Center)+    * (8.b) Sent to Customer: subscription canceled for non-payment: sent S days after 5.a is sent (where "S" is the number of days after which a subscription is cancelled for non-payment, which is set in the [[merchant_guide:notifications|Notification Settings]] area of the Merchant Center)
     * (8.c) Sent to Customer: confirmation of subscription cancellation (merchant canceled the subscription: e.g. violation of certain terms of the Merchant’s Terms and Conditions, unrelated to billing).     * (8.c) Sent to Customer: confirmation of subscription cancellation (merchant canceled the subscription: e.g. violation of certain terms of the Merchant’s Terms and Conditions, unrelated to billing).
     * (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)
Line 76: 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 
  
  
Line 91: 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 ===== ===== Related articles =====
Line 97: Line 108:
   * Notifications sent via [[merchant_guide:notifications_list_callbackurl|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.   * Notifications sent via [[merchant_guide:notifications_list_callbackurl|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.
   * [[developer_guide:developer_guide|SubscriptionBridge API home]]   * [[developer_guide:developer_guide|SubscriptionBridge API home]]
- 
merchant_guide/notifications_list.1271096765.txt.gz · Last modified: 2010/04/12 00:00 (external edit)