Difference between revisions of "NATS4 MEMBER EXPIRE PAD"
From TMM Wiki
Jump to navigationJump to search| (32 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
}} | }} | ||
| − | == | + | == Expire Padding == |
| − | + | Member Expire Padding has the ability to postpone a member's expiration date for a set number of days. This is useful as it allows for possible delays in processing transactions from the biller: insufficient funds, time zone differences, etc. This way, the member does not lose access just because the biller did not process their rebill yet. 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 [[NATS]] has not heard from the processor at all. | |
| − | + | '''Prior to NATS 5.0.2.6, the default is MEMBER_EXPIRE_PAD_DAYS (1). This will add 1 (one) day to all memberships.'''<br> | |
| + | '''As of NATS 5.0.2.6, the default for NEW installs is MEMBER_EXPIRE_PAD. Existing installs are not affected by this change. This will add up to 50% to the membership length with a minimum of 1 (one) day and the maximum of 7 (seven) days 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''. | ||
[[File:EXPIRE PAD.png|500px|Configuring EXPIRE_PAD in NATS4]] | [[File:EXPIRE PAD.png|500px|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_DAYS'' | + | *'''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. |
| − | |||
| − | MEMBER_EXPIRE_PAD | ||
Changing this feature will affect all transactions going forward, but will not modify the current expire dates for existing members. | Changing this feature will affect all transactions going forward, but will not modify the current expire dates for existing members. | ||
| Line 21: | Line 22: | ||
== Custom Biller Padding == | == 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 of 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 | + | For example: You have your ''MEMBER_EXPIRE_PAD'' set to three days, but you notice that ''EXAMPLEBILLER'' always needs four days to process your rebills. Therefore, you can set your [[NATS]] to give ''EXAMPLEBILLER'' 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 | + | To configure member expiration for a specific biller, scroll down 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 shortname'', and ''MEMBER_EXPIRE_PAD_Biller's shortname_DAYS.'' |
[[File:EXPIRE PAD BILLER.png|450px|Configuring Biller Specific Expire Pads NATS4]] | [[File:EXPIRE PAD BILLER.png|450px|Configuring Biller Specific Expire Pads NATS4]] | ||
| − | + | *'''MEMBER_EXPIRE_PAD_''Biller's 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_<biller>'' box is checked, [[NATS]] will ignore any number entered in the ''MEMBER_EXPIRE_PAD<biller>_DAYS'' box. Biller settings (''MEMBER_EXPIRE_PAD_<biller>'' and ''MEMBER_EXPIRE_PAD_<biller>_DAYS'') take precedence over the global settings (''MEMBER_EXPIRE_PAD'' and ''MEMBER_EXPIRE_PAD_DAYS'') | |
| − | + | *'''MEMBER_EXPIRE_PAD_''Biller's shortname''_DAYS''' - Adds a flat number of days to delay membership expiration, regardless of membership length. | |
| − | + | *'''SET_EXPIRE_''Biller's 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. | ||
[[Category:NATS4 Configuration Admin]] | [[Category:NATS4 Configuration Admin]] | ||
Latest revision as of 11:05, 21 July 2020
Expire Padding
Member Expire Padding has the ability to postpone a member's expiration date for a set number of days. This is useful as it allows for possible delays in processing transactions from the biller: insufficient funds, time zone differences, etc. This way, the member does not lose access just because the biller did not process their rebill yet. 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 NATS has not heard from the processor at all.
Prior to NATS 5.0.2.6, the default is MEMBER_EXPIRE_PAD_DAYS (1). This will add 1 (one) day to all memberships.
As of NATS 5.0.2.6, the default for NEW installs is MEMBER_EXPIRE_PAD. Existing installs are not affected by this change. This will add up to 50% to the membership length with a minimum of 1 (one) day and the maximum of 7 (seven) days 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.
- 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 of 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 EXAMPLEBILLER always needs four days to process your rebills. Therefore, you can set your NATS to give EXAMPLEBILLER 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 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 shortname, and MEMBER_EXPIRE_PAD_Biller's shortname_DAYS.
- MEMBER_EXPIRE_PAD_Biller's 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_<biller> box is checked, NATS will ignore any number entered in the MEMBER_EXPIRE_PAD<biller>_DAYS box. Biller settings (MEMBER_EXPIRE_PAD_<biller> and MEMBER_EXPIRE_PAD_<biller>_DAYS) take precedence over the global settings (MEMBER_EXPIRE_PAD and MEMBER_EXPIRE_PAD_DAYS)
- MEMBER_EXPIRE_PAD_Biller's shortname_DAYS - Adds a flat number of days to delay membership expiration, regardless of membership length.
- SET_EXPIRE_Biller's 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.
