Difference between revisions of "NATS4 MEMBER EXPIRE PAD"

From TMM Wiki
Jump to navigationJump to search
Line 5: Line 5:
 
== Expire Padding ==
 
== Expire Padding ==
  
Member Expire Padding provides the ability to prevent [[Ct#Member|member]] accounts from expiring until several days after their payment is due. This is useful as it allows for delays in processing transactions from the [[Ct#Biller|biller]] due to possible delays in receiving rebills-- time zone differences, delays in biller processing, etc. This does not delay the actual payment due date, and it does not give the member extra access if the processor reports an explicit cancel or expire. This feature simply gives the member extra days in case we have not heard from the processor at all. '''By default, [[NATS]] is configured to add 1(one) day of expire padding to all memberships.'''
+
Member Expire Padding provides the ability to prevent [[Ct#Member|member]] accounts from [[Ct#Expire|expiring]] until several days after payment is due. This is useful as it allows for delays in processing transactions from the [[Ct#Biller|biller]] due to possible delays in receiving rebills-- time zone differences, delays in biller processing, etc. This does not delay the actual payment due date, and it does not give the member extra access if the processor reports an explicit cancel or expire. This feature simply gives the member extra days in case we have not heard from the processor at all. '''By default, [[NATS]] is configured to add 1(one) day of expire padding to all memberships.'''
  
 
To change the configuration of this feature, go to the [[NATS4 Configuration Admin]] and select "Billers" from the Current Section drop-down list at the top of the page.  You should then see two fields regarding expire pads: ''MEMBER_EXPIRE_PAD'' and ''MEMBER_EXPIRE_PAD_DAYS''.
 
To change the configuration of this feature, go to the [[NATS4 Configuration Admin]] and select "Billers" from the Current Section drop-down list at the top of the page.  You should then see two fields regarding expire pads: ''MEMBER_EXPIRE_PAD'' and ''MEMBER_EXPIRE_PAD_DAYS''.

Revision as of 16:38, 4 June 2012

NATS 4
Members Admin
The Members Admin
View Member Details
Add Member
MySQL Auth
Mod Authn DB
Multisite Access
Member Logging
Member Password Retrieval
OpenID Connect
Mod Auth OpenIDC
ID Numbers
NATS Configuration Admin
The Configuration Admin
Log Admin Activity
IP Address Filtering
MEMBER_EXPIRE_PAD
SKIP COUNTRIES
Fraud Configuration
Email Configuration
Affiliate Signup Email
Affiliate Postback
Affiliate Postback NEW
Affiliate Analytics
Throttling
NATS4 Terms of Service feature
GeoIP2

Expire Padding

Member Expire Padding provides the ability to prevent member accounts from expiring until several days after payment is due. This is useful as it allows for delays in processing transactions from the biller due to possible delays in receiving rebills-- time zone differences, delays in biller processing, etc. This does not delay the actual payment due date, and it does not give the member extra access if the processor reports an explicit cancel or expire. This feature simply gives the member extra days in case we have not heard from the processor at all. By default, NATS is configured to add 1(one) day of expire padding to all memberships.

To change the configuration of this feature, go to the NATS4 Configuration Admin and select "Billers" from the Current Section drop-down list at the top of the page. You should then see two fields regarding expire pads: MEMBER_EXPIRE_PAD and MEMBER_EXPIRE_PAD_DAYS.


Configuring EXPIRE_PAD in NATS4

  • MEMBER_EXPIRE_PAD_DAYS - Adds a flat number of days to delay membership expiration, regardless of membership length.
  • MEMBER_EXPIRE_PAD - Delays expiration by 50%, with a minimum of one day and a maximum of seven days. For example, a ten-day membership will not expire until the fifteenth day, a three-day trial membership will not expire until the fifth day, a thirty day trial will not expire until the thirty-seventh day, etc. If the MEMBER_EXPIRE_PAD box is checked, NATS will ignore any number entered in the MEMBER_EXPIRE_PAD_DAYS box.

Changing this feature will affect all transactions going forward, but will not modify the current expire dates for existing members.

Custom Biller Padding

Rather than having the same expire pad for every biller, NATS allows you to create custom expire pads for specific billers. This allows you to delay member expiration by a specific number days for members who paid for their membership through a specific biller.

For example: You have your MEMBER_EXPIRE_PAD set to three days, but you notice that EXAMPLE_BILLER always needs four days to process your rebills. Therefore, you can set your NATS to give EXAMPLE_BILLER a four day pad, and your remaining billers would still have the three day pad.

To configure member expiration for a specific biller, scroll down on the Biller Configurations page to the specific biller you wish to customize. Each biller will have their own specific expire pad fields-- MEMBER_EXPIRE_PAD_(Biller's name), and MEMBER_EXPIRE_PAD_(Billers name)DAYS.


Configuring Biller Specific Expire Pads NATS4

  • MEMBER_EXPIRE_PAD_Billers shortname - Delays expiration by for this biller by 50%, with a minimum of one day and a maximum of seven days. For example, a ten-day membership will not expire until the fifteenth day, a three-day trial membership will not expire until the fifth day, a thirty day trial will not expire until the thirty-seventh day, etc. If the MEMBER_EXPIRE_PAD box is checked, NATS will ignore any number entered in the MEMBER_EXPIRE_PAD_DAYS box.
  • MEMBER_EXPIRE_PAD_Billers shortname_DAYS - Adds a flat number of days to delay membership expiration, regardless of membership length.
  • SET_EXPIRE_Billers shortname_DATE - How the expire pad date is to be determined. The default setting for every biller is "NATS set". Through the drop down menu, this can be set to:
    • NATS set - The expire pad length is determined by what has been set in NATS. This is the default setting.
    • Biller set - The expire pad length is determined by what the specific biller has specified their pad to be, and the NATS configurations are ignored.
    • Earliest - The expire pad length is either what is set in NATS or what is set by the biller, whichever occurs earler.
    • Latest - The expire pad length is either what is set in NATS or what is set by the biller, whichever occurs later.