Difference between revisions of "How It Works"

From aMember Pro Documentation
Jump to: navigation, search
m
Line 1: Line 1:
<h2>Signup</h2>
+
<h2>What aMember Pro is all about</h2>
You need to register in order to start using the great features that AMember has to offer. This can be done by filling in a simple signup form. To Register:
+
aMember Pro is a membership/subscription management PHP script. It is installed to your website to provide the following functionality:
 +
* user registration
 +
* process customer payments and keep tracks of them
 +
* protect website folders, pages, downloads, and other kind of content making it available for subscribed users only
 +
* integration of users database with third-party scripts
 +
* affiliate program management
 +
* simple helpdesk functionality to provide easy communication betweeen customers and site administrators
 +
* manage opt-in e-mail lists and send mass e-mails to customers
  
#Go to http://www.yoursite.int/amember/signup.php.
+
<h2>Ordering Process</h2>
#Enter your name and email address in the fields provided. These are required fields and need to be filled in.
+
To order a subscription or product within aMember Pro, user must fill-in signup form generated by aMember or log-in to existing account. Once customer presses the signup button, aMember Pro creates the following records in database:
#If the automatic username and password settings have not been enabled, you may have to enter a username and password.
+
* pending user record
#Fill in any or all of the the optional information you would like to provide.
+
* pending invoice record
#Once you have filled in all relevant information, click on the "Signup" button to submit the form. When you submit the form, two database records are created in AMember as follows:
+
''  Note: At this point user account is not activated. Until the payment is competed, user will not be able to view or download protected content. He can, however, login to member area to make new payment if first payment attempt was failed''
#* a pending user record
+
#* a pending payment record.
+
+
''  Note: At this point your account is not activated. The pending payment record contains amount to be paid, subscription start and expiry dates, subscription type ordered and other related information. Until the payment is competed, you will not be able enter information in AMember''
+
  
<h2>Actual Payment</h2>
+
Once these records are created, aMember redirects customer to payment system to make actual payment and passes payment amount and subscription settings to it. The payment gateway (eg. PayPal, 2Checkout or Authorize.Net) checks the information entered and makes the transaction.
Once you click the Signup button, the payment system page is displayed.  
+
# When the transaction is completed successfully, the system will display a confirmation of payment. At this point, the system sends confirmation of the payment to the aMember script and the user's status is changed from "Pending" to "Active". User will receive a welcome email with details about username and possibly other information (e-mail template can be customized by site administrator).
 +
# If the transaction fails, the failed payment page will be displayed, and most payment systems will redirect customer to aMember "cancelled" payment page, where user can choose another method of payment to repeat subscription attempt.
  
# Select the method of payment.
+
<h2>Expiration</h2>
# Enter the payment information using the fields provided.
+
Depending on product settings configured by site administrator, user access may expire. For example, site administrator may choose to sell subscriptions to 30 days for $10.99. Then, if subscription is not recurring, customer record will ''expire''. User will be marked as ''Expired'', and protected content access will be revoked. However, user record is not deleted after expiration, so customer may back to the website, login to his account and renew subscription - by placing new order.
# Submit the information.
+
 
# The payment gateway (eg PayPal, 2Checkout or Authorize.Net) checks the information entered and makes the transaction.
+
<h2>Recurring Billing</h2>
# When the transaction is completed successfully, the system will display a confirmation of payment. At this point, the system sends confirmation of the payment to the AMember script and the user's status is changed from "Pending" to Paid". You will receive a welcome email with details about your username, password, login links, etc.  
+
Many payment processors allows to setup so-named "recurring" billing. This way customer is billed automatically - configured money amount every configured period (eg. $20 every month). aMember Pro was designed to handle recurring billing, so these payments will be correctly processed. Most payment processors reports to aMember when successful recurring payment has made and aMember extends user subscription accordingly. In this case entire membership management is automated.
# If the transaction fails, the failed payment page will be displayed.
+
<h3>Recurring Billing Cancellations</h3>
 +
Sometimes user wants to unsubscribe from recurring subscription. It can be done by either a link in aMember members area, or in payment processor (for example PayPal provides ability to cancel recurring subscriptions within user account). In this case, aMember will be notified about cancellation and customer invoice will be maked as "Cancelled". It does not mean, however, that user looses access immediately. User will still have access to protected content until paid period expires.
 +
 
 +
<h2>Refunds and Chargebacks</h2>
 +
In case if refunds and chargebacks are reported to aMember, aMember will automatically keep records of this, and revoke customer access to protected content.

Revision as of 15:54, 26 October 2011

Contents

What aMember Pro is all about

aMember Pro is a membership/subscription management PHP script. It is installed to your website to provide the following functionality:

  • user registration
  • process customer payments and keep tracks of them
  • protect website folders, pages, downloads, and other kind of content making it available for subscribed users only
  • integration of users database with third-party scripts
  • affiliate program management
  • simple helpdesk functionality to provide easy communication betweeen customers and site administrators
  • manage opt-in e-mail lists and send mass e-mails to customers

Ordering Process

To order a subscription or product within aMember Pro, user must fill-in signup form generated by aMember or log-in to existing account. Once customer presses the signup button, aMember Pro creates the following records in database:

  • pending user record
  • pending invoice record

Note: At this point user account is not activated. Until the payment is competed, user will not be able to view or download protected content. He can, however, login to member area to make new payment if first payment attempt was failed

Once these records are created, aMember redirects customer to payment system to make actual payment and passes payment amount and subscription settings to it. The payment gateway (eg. PayPal, 2Checkout or Authorize.Net) checks the information entered and makes the transaction.

  1. When the transaction is completed successfully, the system will display a confirmation of payment. At this point, the system sends confirmation of the payment to the aMember script and the user's status is changed from "Pending" to "Active". User will receive a welcome email with details about username and possibly other information (e-mail template can be customized by site administrator).
  2. If the transaction fails, the failed payment page will be displayed, and most payment systems will redirect customer to aMember "cancelled" payment page, where user can choose another method of payment to repeat subscription attempt.

Expiration

Depending on product settings configured by site administrator, user access may expire. For example, site administrator may choose to sell subscriptions to 30 days for $10.99. Then, if subscription is not recurring, customer record will expire. User will be marked as Expired, and protected content access will be revoked. However, user record is not deleted after expiration, so customer may back to the website, login to his account and renew subscription - by placing new order.

Recurring Billing

Many payment processors allows to setup so-named "recurring" billing. This way customer is billed automatically - configured money amount every configured period (eg. $20 every month). aMember Pro was designed to handle recurring billing, so these payments will be correctly processed. Most payment processors reports to aMember when successful recurring payment has made and aMember extends user subscription accordingly. In this case entire membership management is automated.

Recurring Billing Cancellations

Sometimes user wants to unsubscribe from recurring subscription. It can be done by either a link in aMember members area, or in payment processor (for example PayPal provides ability to cancel recurring subscriptions within user account). In this case, aMember will be notified about cancellation and customer invoice will be maked as "Cancelled". It does not mean, however, that user looses access immediately. User will still have access to protected content until paid period expires.

Refunds and Chargebacks

In case if refunds and chargebacks are reported to aMember, aMember will automatically keep records of this, and revoke customer access to protected content.