docs(api): clarify simulate_clearing behavior in transactions

Author: stainless-app[bot]

.stats.yml

@@ -1,4 +1,4 @@
 configured_endpoints: 213
-openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/lithic/lithic-9e397c65ffb81e2928b8ecf979769a79131ae6058b6fb373a5e930dc8a168732.yml
-openapi_spec_hash: 93aea3855d2d1c390107d223762aa818
+openapi_spec_url: https://storage.googleapis.com/stainless-sdk-openapi-specs/lithic/lithic-1514911f233cb8bf0d6752c45bfa53a61b8f9b8ff215a4ea94a95f9505911000.yml
+openapi_spec_hash: 9820a9c9a4ff778c627041eb53fd4ee5
 config_hash: 5bb913c05ebeb301ec925b16e75bb251

src/lithic/resources/transactions/transactions.py

@@ -470,9 +470,10 @@ def simulate_clearing(
         After this event, the
         transaction transitions from `PENDING` to `SETTLED` status.
 
-        If `amount` is not set, the full amount of the transaction will be cleared.
-        Transactions that have already cleared, either partially or fully, cannot be
-        cleared again using this endpoint.
+        If `amount` is not set, the full amount of the transaction will be cleared. This
+        endpoint may be called multiple times against the same authorization to simulate
+        a multiple-completion scenario, with each call creating a separate clearing
+        event.
 
         Args:
           token: The transaction token returned from the /v1/simulate/authorize response.
@@ -483,9 +484,10 @@ def simulate_clearing(
               example, entering 100 in this field will result in a -100 amount in the
               transaction, if the original authorization is a credit authorization.
 
-              If `amount` is not set, the full amount of the transaction will be cleared.
-              Transactions that have already cleared, either partially or fully, cannot be
-              cleared again using this endpoint.
+              If `amount` is not set, the full amount of the transaction will be cleared. This
+              endpoint may be called multiple times against the same authorization to simulate
+              a multiple-completion scenario, with each call creating a separate clearing
+              event.
 
           extra_headers: Send extra headers
 
@@ -1214,9 +1216,10 @@ async def simulate_clearing(
         After this event, the
         transaction transitions from `PENDING` to `SETTLED` status.
 
-        If `amount` is not set, the full amount of the transaction will be cleared.
-        Transactions that have already cleared, either partially or fully, cannot be
-        cleared again using this endpoint.
+        If `amount` is not set, the full amount of the transaction will be cleared. This
+        endpoint may be called multiple times against the same authorization to simulate
+        a multiple-completion scenario, with each call creating a separate clearing
+        event.
 
         Args:
           token: The transaction token returned from the /v1/simulate/authorize response.
@@ -1227,9 +1230,10 @@ async def simulate_clearing(
               example, entering 100 in this field will result in a -100 amount in the
               transaction, if the original authorization is a credit authorization.
 
-              If `amount` is not set, the full amount of the transaction will be cleared.
-              Transactions that have already cleared, either partially or fully, cannot be
-              cleared again using this endpoint.
+              If `amount` is not set, the full amount of the transaction will be cleared. This
+              endpoint may be called multiple times against the same authorization to simulate
+              a multiple-completion scenario, with each call creating a separate clearing
+              event.
 
           extra_headers: Send extra headers
 

src/lithic/types/transaction_simulate_clearing_params.py

@@ -20,7 +20,8 @@ class TransactionSimulateClearingParams(TypedDict, total=False):
     will result in a -100 amount in the transaction, if the original authorization
     is a credit authorization.
 
-    If `amount` is not set, the full amount of the transaction will be cleared.
-    Transactions that have already cleared, either partially or fully, cannot be
-    cleared again using this endpoint.
+    If `amount` is not set, the full amount of the transaction will be cleared. This
+    endpoint may be called multiple times against the same authorization to simulate
+    a multiple-completion scenario, with each call creating a separate clearing
+    event.
     """