Difference between revisions of "NATS4 MEMBER EXPIRE PAD"
Line 7: | Line 7: | ||
MEMBER_EXPIRE_PAD, implemented in [[NATS]] 3.1, provides the ability to prevent [[Ct#Member|member]] accounts from expiring until several days after their payment was due. This is useful as it allows for delays in processing transactions from the [[Ct#Biller|biller]]. 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. | MEMBER_EXPIRE_PAD, implemented in [[NATS]] 3.1, provides the ability to prevent [[Ct#Member|member]] accounts from expiring until several days after their payment was due. This is useful as it allows for delays in processing transactions from the [[Ct#Biller|biller]]. 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 expiration delay to all memberships. To | + | By default, [[NATS]] is configured to add 1(one) day of expiration delay 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 options 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 amount of days to delay membership expiration, regardless of membership length. | ||
+ | If the MEMBER_EXPIRE_PAD box is checked, [[NATS]] will delay 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. | Changing this feature will affect all transactions going forward, but will not modify the current expire dates for existing members. |
Revision as of 11:38, 4 June 2012
MEMBER_EXPIRE_PAD
MEMBER_EXPIRE_PAD, implemented in NATS 3.1, provides the ability to prevent member accounts from expiring until several days after their payment was due. This is useful as it allows for delays in processing transactions from the biller. 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 expiration delay 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 options regarding expire pads: MEMBER_EXPIRE_PAD and MEMBER_EXPIRE_PAD_DAYS.
MEMBER_EXPIRE_PAD_DAYS adds a flat amount of days to delay membership expiration, regardless of membership length.
If the MEMBER_EXPIRE_PAD box is checked, NATS will delay 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 Padding
Billers that support a custom pad date include Epoch, Jettis, and NetCash.
For example: Epoch allows you to delay member expiration by three days if they paid for their membership through them.
Keep in mind, however, that the MEMBER_EXPIRE_PAD setting will not override any custom pad dates from Epoch, Jettis, and NetCash. If you would like to enable a biller's custom pad date, please enter a request in our Too Much Media ticketing system.