added

Custom Calendar Cycles Now Available for Velocity Limit Rules

Release Date

September 25, 2025

Products Affected

Velocity Limits API, Lithic Dashboard

Impact

Enhanced period object format for velocity rules

Audience

All customers using velocity limits

Action Required

Migrate to new format by November 3, 2025

Overview

Beginning September 25th, velocity limits support custom calendar cycles that enable card programs to specify when weekly, monthly, and yearly limits reset. This enhancement provides greater flexibility for aligning spending controls with business requirements, such as matching corporate billing cycles or payroll schedules.

Details

The velocity limit configuration now accepts an enhanced period object that specifies both the limit type and reset timing. Programs can customize when limits reset rather than defaulting to standard calendar boundaries.

Supported Customizations

  • Weekly limits: Specify the day of week for reset (1-7, where 1 is Monday per ISO-8601)
  • Monthly limits: Specify the day of month for reset (1-31)
  • Yearly limits: Specify the month (1-12) and day of month (1-31) for reset

API Format Changes

Previously, velocity limits used a string format for the period:

{
    "scope": "CARD",
    "period": "WEEK",
    "limit_amount": 100000000
}

The new format uses an object structure to specify reset timing:

{
    "scope": "CARD",
    "period": {
        "type": "WEEK",
        "day_of_week": 3
    },
    "limit_amount": 100000000
}

In this example, the weekly limit resets on Wednesday (day 3 per ISO-8601 standard).

Lithic Dashboard Changes

This new functionality is also now available when creating rules via the Lithic Dashboard.

When creating or editing a velocity limit rule, programs can now set Custom Cycle Schedule for calendar period time periods.


Release Timeline

  • Production availability: September 25, 2025
  • Deprecation deadline: November 3, 2025

The string format for creating velocity limit rules remains functional but is now deprecated. Both formats are currently accepted for creating velocity limit rules. String format support ends November 3, 2025; object format will be required after this date.

User Impact

Programs must update their integration to use the object format when creating or updating new velocity limit rules after November 3, 2025. No action is required to update rules already in place.

Updated Documentation

For detailed API specifications and migration examples, visit our API Reference.

If you have any questions or concerns, please contact us via the HELP link in your Lithic Dashboard.


The Lithic changelog has an RSS feed! To monitor for new update announcements, subscribe with your preferred RSS reader.