Subscription and settings.
Array of allowed frequencies.
Finds which next transaction date modification rules are applicable to the given subscription and merges them together.
Subscription to generate constraints for.
Next date modification config from the customer portal settings.
Returns true if all modifications are allowed, false if next date can't be changed by the customer, object with constraints in any other case.
Gives a rough estimate for a number of milliseconds in the given frequency.
IMPORTANT: this function SHOULD NOT be used to calculate precise dates as it doesn't account for leap years, months of variable length, etc. It works best for broad estimates and comparing frequencies.
Frequency as positive integer + units (y, m, w, d for years, months, weeks and days respectively). You can use .5m for twice a month. Example: 1m (1 month), 4y (4 years).
Estimated number of milliseconds in the given frequency.
Checks if given date (YYYY-MM-DD) can be used as the next transaction date for given subscription.
Subscription, customer portal settings and value.
True if given date can be used as next transaction date.
Generated using TypeDoc
Returns allowed frequencies for given subscription and customer portal settings.