Tweet
Release date: January 20, 2013
Version #: FaaS.x.20130117.001.031.000.000.030
New Feature(s)
The following special treatment is provided for convenience:
A payment form may ask the patron to start her payment on a specific date, e.g. beginning of the month. In this case regardless of the day of the month that the payment is being initiated the payment will be charged on the first of the month. If the requested day is invalid (February 31) an error will be returned as invalid date so it is important that the form does not allow for invalid dates to be set for processing.
Please note:
Initiating a payment on the 31st of the month will set the payment to be processed on the first month that has 31 days.
Here are a few examples:
Example 1:
Example 2:
Example 3:
Example 4:
Recommendation:
A typical scenario is when a donor wishes to start a recurring payment but wants the payment to be processed on the first of each month and continue every month, e.g. January 1, February 1, March 1, etc.
In such a case it is recommended that the only value that is passed be the ChargeDateDay and the rest not be posted. The following node needs to be added:
If a pull down menu is to be provided for selecting the date it is strongly recommended that the pull down menu does not offer 29, 30, 31 as available days to avoid problems with such months as February, April, etc.
Version #: FaaS.x.20130117.001.031.000.000.030
New Feature(s)
- Recurring period: Addition of Week as a period- read more: https://manual.clickandpledge.com/Fo...g_Transactions
- Item campaign: Campaign node may be added for each Item in the form: Campaign1, Campaign2, etc. read more: https://manual.clickandpledge.com/Fo...ct_Information
- ChargeDate (Optional parameters) - read more: https://manual.clickandpledge.com/Fo...tml#ChargeDate
- ChargeDateYear: The year for the first transaction (may be left blank)
- ChargeDateMonth: The month for the first transaction (may be left blank)
- ChargeDateDay: The day for the first transaction
The following special treatment is provided for convenience:
- Charge date Year: If YEAR is NOT passed the current YEAR will be assumed by default
- Charge date Month: If MONTH Is NOT passed the current MONTH will be assumed by default
A payment form may ask the patron to start her payment on a specific date, e.g. beginning of the month. In this case regardless of the day of the month that the payment is being initiated the payment will be charged on the first of the month. If the requested day is invalid (February 31) an error will be returned as invalid date so it is important that the form does not allow for invalid dates to be set for processing.
Please note:
Initiating a payment on the 31st of the month will set the payment to be processed on the first month that has 31 days.
Here are a few examples:
Example 1:
- Transaction date: January 2, 2013
- Request processing date: 1st of the month
- Transaction will process on February 1, 2013
Example 2:
- Transaction date: January 2, 2013
- Request processing date: 31st of the month
- Transaction will process on March 31, 2013
Example 3:
- Transaction date: January 2, 2013
- Request processing date: January 1
- Transaction will process on January 1, 2014
Example 4:
- Transaction date: January 2, 2013
- Request processing date: 3rd day of the month
- Transaction will process on January 3, 2013
Recommendation:
A typical scenario is when a donor wishes to start a recurring payment but wants the payment to be processed on the first of each month and continue every month, e.g. January 1, February 1, March 1, etc.
In such a case it is recommended that the only value that is passed be the ChargeDateDay and the rest not be posted. The following node needs to be added:
If a pull down menu is to be provided for selecting the date it is strongly recommended that the pull down menu does not offer 29, 30, 31 as available days to avoid problems with such months as February, April, etc.