What changed from legacy to standardized behaviour

Before the timezone standardization initiative, date-time behaviour across Capillary modules was inconsistent:

Some fields used legacy formats (not ISO 8601).
Timezone offsets were not preserved from input.
The awarded date for points could reflect either server or store timezone, depending on the scenario.
Event notifications did not include millisecond equivalents.

The standardized model introduced:

ISO 8601 as the universal format for GET API responses.
Shadow fields (for example, dateISO alongside date) for backward compatibility on legacy fields.
Offset preservation fields (billingTimeInputOffset, eventDateTimeInputOffset) for transactions and behavioural events.
Epoch milliseconds for behavioural events and event notifications.
*InMillis shadow fields for event notification date-time fields not already in milliseconds.

Backward compatibility: All legacy fields are retained. Shadow fields are additive. Existing integrations continue to work without changes.

Organization availability

Organization type	Standardized timezone behaviour
Created from 2026 onwards	Enabled by default. No action required.
Created before 2026	Standardized API formats and response fields are already available. However, certain configurations controlling UI and Loyalty processing behaviour are gated and may remain disabled.

How to check if standardized timezone is enabled for your organization

Navigate to Organization Settings > Organization Profile.
Check whether a timezone is configured under Set Org TimeZone.
To confirm whether the TIMEZONE_ENABLED flag is active for your organization, raise a support ticket with the Capillary Product Support team.

How to enable standardized timezone for older organizations

For organizations created before 2026, raise a support ticket with the Capillary Product Support team and request that the TIMEZONE_ENABLED configuration flag be enabled.

Once enabled, the standardized model applies to new data from that point forward. Historical data is not retroactively modified.

Optional configuration: Disabling automatic timezone conversion (v2 APIs only)

If required, you can disable automatic conversion of transaction time to the server timezone for v2 Transaction APIs. To activate this, raise a request with the Capillary Product Support team to enable:

CONF_ORG_DISABLE_MACHINE_TIME_CONV

When enabled:

The billing time from the request payload is stored as provided.
No conversion to UTC or server timezone is performed.
The UTC offset in the input is not applied during storage.

This configuration applies only to v2 Transaction APIs and should be enabled only after assessing its impact on downstream integrations.

Billing time	v2 GET (API response)
`2026-01-23T09:00:00+05:30`	`2026-01-23 09:00:00`