feat(client): adds support for 3DS to Auth Rules

- Auth Rules now support decisioning on 3DS authentications: https://docs.lithic.com/changelog/may-28-2025

Author: stainless-app[bot]

.stats.yml

@@ -1,4 +1,4 @@
 configured_endpoints: 160
-openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/lithic%2Flithic-025f40c854a9485cf316c9058f9cc5fa37f069add30e409d49ab93f2e166f4fb.yml
-openapi_spec_hash: a9391f3a54b8db5d5df40169de8c645c
+openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/lithic%2Flithic-89dfdedd460a673d9addf6d763389f59895e986036296d99baf89366ba622034.yml
+openapi_spec_hash: b6183fb775fc8bfa3d40ed7130b17976
 config_hash: fa3481d1d8505e4157f6cebe93211bd0

src/lithic/resources/accounts.py

@@ -117,8 +117,8 @@ def update(
 
           verification_address: Address used during Address Verification Service (AVS) checks during
               transactions if enabled via Auth Rules. This field is deprecated as AVS checks
-              are no longer supported by Authorization Rules. The field will be removed from
-              the schema in a future release.
+              are no longer supported by Auth Rules. The field will be removed from the schema
+              in a future release.
 
           extra_headers: Send extra headers
 
@@ -344,8 +344,8 @@ async def update(
 
           verification_address: Address used during Address Verification Service (AVS) checks during
               transactions if enabled via Auth Rules. This field is deprecated as AVS checks
-              are no longer supported by Authorization Rules. The field will be removed from
-              the schema in a future release.
+              are no longer supported by Auth Rules. The field will be removed from the schema
+              in a future release.
 
           extra_headers: Send extra headers
 

src/lithic/resources/auth_rules/v2/backtests.py

@@ -55,16 +55,15 @@ def create(
         timeout: float | httpx.Timeout | None | NotGiven = NOT_GIVEN,
     ) -> BacktestCreateResponse:
         """
-        Initiates a request to asynchronously generate a backtest for an authorization
-        rule. During backtesting, both the active version (if one exists) and the draft
-        version of the Authorization Rule are evaluated by replaying historical
-        transaction data against the rule's conditions. This process allows customers to
-        simulate and understand the effects of proposed rule changes before deployment.
-        The generated backtest report provides detailed results showing whether the
-        draft version of the Auth Rule would have approved or declined historical
-        transactions which were processed during the backtest period. These reports help
-        evaluate how changes to rule configurations might affect overall transaction
-        approval rates.
+        Initiates a request to asynchronously generate a backtest for an Auth rule.
+        During backtesting, both the active version (if one exists) and the draft
+        version of the Auth Rule are evaluated by replaying historical transaction data
+        against the rule's conditions. This process allows customers to simulate and
+        understand the effects of proposed rule changes before deployment. The generated
+        backtest report provides detailed results showing whether the draft version of
+        the Auth Rule would have approved or declined historical transactions which were
+        processed during the backtest period. These reports help evaluate how changes to
+        rule configurations might affect overall transaction approval rates.
 
         The generated backtest report will be delivered asynchronously through a webhook
         with `event_type` = `auth_rules.backtest_report.created`. See the docs on
@@ -124,7 +123,7 @@ def retrieve(
         timeout: float | httpx.Timeout | None | NotGiven = NOT_GIVEN,
     ) -> BacktestResults:
         """
-        Returns the backtest results of an authorization rule (if available).
+        Returns the backtest results of an Auth rule (if available).
 
         Backtesting is an asynchronous process that requires time to complete. If a
         customer retrieves the backtest results using this endpoint before the report is
@@ -140,8 +139,8 @@ def retrieve(
         also always represent the configuration of the rule at the time requests are
         made to this endpoint. For example, the results for `current_version` in the
         served backtest report will be consistent with which version of the rule is
-        currently activated in the Auth Stream, regardless of which version of the rule
-        was active in the Auth Stream at the time a backtest is requested.
+        currently activated in the respective event stream, regardless of which version
+        of the rule was active in the event stream at the time a backtest is requested.
 
         Args:
           extra_headers: Send extra headers
@@ -201,16 +200,15 @@ async def create(
         timeout: float | httpx.Timeout | None | NotGiven = NOT_GIVEN,
     ) -> BacktestCreateResponse:
         """
-        Initiates a request to asynchronously generate a backtest for an authorization
-        rule. During backtesting, both the active version (if one exists) and the draft
-        version of the Authorization Rule are evaluated by replaying historical
-        transaction data against the rule's conditions. This process allows customers to
-        simulate and understand the effects of proposed rule changes before deployment.
-        The generated backtest report provides detailed results showing whether the
-        draft version of the Auth Rule would have approved or declined historical
-        transactions which were processed during the backtest period. These reports help
-        evaluate how changes to rule configurations might affect overall transaction
-        approval rates.
+        Initiates a request to asynchronously generate a backtest for an Auth rule.
+        During backtesting, both the active version (if one exists) and the draft
+        version of the Auth Rule are evaluated by replaying historical transaction data
+        against the rule's conditions. This process allows customers to simulate and
+        understand the effects of proposed rule changes before deployment. The generated
+        backtest report provides detailed results showing whether the draft version of
+        the Auth Rule would have approved or declined historical transactions which were
+        processed during the backtest period. These reports help evaluate how changes to
+        rule configurations might affect overall transaction approval rates.
 
         The generated backtest report will be delivered asynchronously through a webhook
         with `event_type` = `auth_rules.backtest_report.created`. See the docs on
@@ -270,7 +268,7 @@ async def retrieve(
         timeout: float | httpx.Timeout | None | NotGiven = NOT_GIVEN,
     ) -> BacktestResults:
         """
-        Returns the backtest results of an authorization rule (if available).
+        Returns the backtest results of an Auth rule (if available).
 
         Backtesting is an asynchronous process that requires time to complete. If a
         customer retrieves the backtest results using this endpoint before the report is
@@ -286,8 +284,8 @@ async def retrieve(
         also always represent the configuration of the rule at the time requests are
         made to this endpoint. For example, the results for `current_version` in the
         served backtest report will be consistent with which version of the rule is
-        currently activated in the Auth Stream, regardless of which version of the rule
-        was active in the Auth Stream at the time a backtest is requested.
+        currently activated in the respective event stream, regardless of which version
+        of the rule was active in the event stream at the time a backtest is requested.
 
         Args:
           extra_headers: Send extra headers