Difference between revisions of "NATS4 MEMBER EXPIRE PAD"
Line 6: | Line 6: | ||
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. | ||
+ | |||
+ | [[File:EXPIRE PAD.png|450px|Configuring EXPIRE_PAD in NATS4]] | ||
For example, trial membership expiration will be delayed by 50%, with a minimum of one day and a maximum of seven days. In this example, a three-day trial membership will not expire until the fifth day. | For example, trial membership expiration will be delayed by 50%, with a minimum of one day and a maximum of seven days. In this example, a three-day trial membership will not expire until the fifth day. | ||
− | |||
− | |||
− | |||
− | |||
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 10:33, 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.
For example, trial membership expiration will be delayed by 50%, with a minimum of one day and a maximum of seven days. In this example, a three-day trial membership will not expire until the fifth day.
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.