| Pricing Plan | Growth |
| Available in | All countries |
This article explains how recurring donations (subscriptions) are charged in the Tamaro Widget and which settings determine the charge schedule.
Overview
A subscription is used to manage recurring donations or payments. It links a supporter to a payment method and automatically creates charges according to a predefined schedule.
Depending on the configuration, subscriptions can be charged:
- Monthly
- Quarterly
- Semi-annually
- Yearly
- According to a custom schedule
Understanding the subscription settings helps ensure recurring donations are collected at the expected time.
What is a subscription?
A subscription contains all information required to process recurring donations or payments.
Typical subscription data includes:
- Supporter information
- Payment method
- Donation amount
- Currency
- Charge interval
- Payment provider
- Subscription status
How charge schedules work
Two settings determine when recurring charges are executed:
- Immediate execution
- Point in interval
Immediate execution
This setting determines whether the first donation is charged immediately when the subscription is created.
Immediate execution = true
The first charge is collected immediately when the subscription is created.
When the next scheduled charge date for the current interval is reached, it is skipped because the supporter has already been charged for that period.
Example
A yearly subscription is created on 18 September 2026.
- First charge: 18 September 2026
- The next scheduled charge within the same interval is skipped
- Future charges continue according to the selected interval setting
Immediate execution = false
No donation is collected when the subscription is created.
Instead, an authorisation transaction may be performed to validate the payment method.
The first actual charge occurs on the next scheduled charge date.
Point in interval
This setting determines when recurring charges are executed within the selected interval.
First of
Charges are executed on the first day of the interval.
Examples:
| Interval | Charge date |
|---|---|
| Monthly | First day of the month |
| Quarterly | First day of the quarter |
| Yearly | First day of the year |
Last of
Charges are executed on the last day of the interval.
Examples:
| Interval | Charge date |
|---|---|
| Monthly | Last day of the month |
| Quarterly | Last day of the quarter |
| Yearly | Last day of the year |
Just in time
Charges are executed on the same calendar date on which the subscription was originally created.
Example
A yearly subscription created on 18 September will be charged on 18 September each year.
Charge schedule examples
Immediate execution = true + Last of
Yearly subscription created on 18 September 2026
- First charge: 18 September 2026
- Charge on 31 December 2026 is skipped
- Next charge: 31 December 2027
Immediate execution = true + First of
Yearly subscription created on 18 September 2026
- First charge: 18 September 2026
- Charge on 1 January 2027 is skipped
- Next charge: 1 January 2028
Immediate execution = true + Just in time
Yearly subscription created on 18 September 2026
- First charge: 18 September 2026
- Charge on 18 September 2027 is skipped
- Next charge: 18 September 2028
Immediate execution = false + Last of
Yearly subscription created on 18 September 2026
- Authorisation transaction performed
- No immediate charge
- First charge: 31 December 2027
- Second charge: 31 December 2028
Immediate execution = false + First of
Yearly subscription created on 18 September 2026
- Authorisation transaction performed
- No immediate charge
- First charge: 1 January 2027
- Second charge: 1 January 2028
Immediate execution = false + Just in time
Yearly subscription created on 18 September 2026
- Authorisation transaction performed
- No immediate charge
- First charge: 18 September 2027
- Second charge: 18 September 2028
|
Note: The same principles apply to monthly, quarterly, and semi-annual subscriptions. |
Subscription statuses
Subscriptions can have different statuses throughout their lifecycle.
| Status | Description |
|---|---|
| pending | A charge has been initiated, but the final result is not yet available. |
| succeeded | The charge was successful. |
| failed | The charge failed. |
| cancelled | The charge was cancelled. |
| refunded | The charge was successful but has been fully refunded. |
| partially_refunded | The charge was successful but only part of the amount was refunded. |
| reversed | The charge was successful but was later charged back. |
Recommended configuration
RaiseNow recommends the following default configuration:
| Setting | Recommended value |
|---|---|
| Immediate execution | false |
| Point in interval | Just in time |
This configuration provides a predictable charging schedule and is fully supported across RaiseNow products.
Need a different charging schedule?
If you would like to use a different subscription configuration or have questions about recurring donation behaviour, contact contact our Customer Success team.
For technical details and advanced configuration options, please refer to our Developer Documentation.
Comments
0 comments
Please sign in to leave a comment.