payabli 3.0.1 → 3.0.3

data/reference.md

@@ -339,8 +339,8 @@ Retrieves a file attached to a bill, either as a binary file or as a Base64-enco
 
 ```ruby
 client.bill.get_attached_from_bill(
-  filename: "0_Bill.pdf",
   id_bill: 285,
+  filename: "0_Bill.pdf",
   return_object: true
 )
 ```
@@ -425,8 +425,8 @@ Delete a file attached to a bill.
 
 ```ruby
 client.bill.delete_attached_from_bill(
-  filename: "0_Bill.pdf",
-  id_bill: 285
+  id_bill: 285,
+  filename: "0_Bill.pdf"
 )
 ```
 </dd>
@@ -673,8 +673,8 @@ Approve or disapprove a bill by ID.
 
 ```ruby
 client.bill.set_approved_bill(
-  approved: "true",
-  id_bill: 285
+  id_bill: 285,
+  approved: "true"
 )
 ```
 </dd>
@@ -1041,7 +1041,7 @@ Example: totalAmount(gt)=20 return all records with totalAmount greater than 20.
 <dl>
 <dd>
 
-Creates a customer in an entrypoint. An identifier is required to create customer records. Change your identifier settings in Settings > Custom Fields in PartnerHub.
+Creates a customer in an entrypoint. An identifier is required to create customer records. Change your identifier settings in Settings > Custom Fields in the Payabli Portal.
 If you don't include an identifier, the record is rejected.
 </dd>
 </dl>
@@ -1179,7 +1179,7 @@ client.customer.get_customer(customer_id: 4440)
 <dl>
 <dd>
 
-**customer_id:** `Integer` — Payabli-generated customer ID. Maps to "Customer ID" column in PartnerHub.
+**customer_id:** `Integer` — Payabli-generated customer ID. Maps to "Customer ID" column in the Payabli Portal.
     
 </dd>
 </dl>
@@ -1250,7 +1250,7 @@ client.customer.update_customer(
 <dl>
 <dd>
 
-**customer_id:** `Integer` — Payabli-generated customer ID. Maps to "Customer ID" column in PartnerHub.
+**customer_id:** `Integer` — Payabli-generated customer ID. Maps to "Customer ID" column in the Payabli Portal.
     
 </dd>
 </dl>
@@ -1320,7 +1320,7 @@ client.customer.delete_customer(customer_id: 4440)
 <dl>
 <dd>
 
-**customer_id:** `Integer` — Payabli-generated customer ID. Maps to "Customer ID" column in PartnerHub.
+**customer_id:** `Integer` — Payabli-generated customer ID. Maps to "Customer ID" column in the Payabli Portal.
     
 </dd>
 </dl>
@@ -1382,7 +1382,7 @@ client.customer.request_consent(customer_id: 4440)
 <dl>
 <dd>
 
-**customer_id:** `Integer` — Payabli-generated customer ID. Maps to "Customer ID" column in PartnerHub.
+**customer_id:** `Integer` — Payabli-generated customer ID. Maps to "Customer ID" column in the Payabli Portal.
     
 </dd>
 </dl>
@@ -1447,7 +1447,7 @@ client.customer.link_customer_transaction(
 <dl>
 <dd>
 
-**customer_id:** `Integer` — Payabli-generated customer ID. Maps to "Customer ID" column in PartnerHub.
+**customer_id:** `Integer` — Payabli-generated customer ID. Maps to "Customer ID" column in the Payabli Portal.
     
 </dd>
 </dl>
@@ -1580,11 +1580,14 @@ client.check_capture.check_processing(
 <dl>
 <dd>
 
+<Warning>
+  This endpoint is deprecated. New integrations should use the [Authorize endpoint](/developers/api-reference/moneyinV2/authorize-a-transaction), then capture, void, or refund the resulting transaction with the corresponding endpoints. Transactions created with this legacy endpoint must be managed with the legacy lifecycle endpoints — they aren't interchangeable with the current ones.
+</Warning>
+
+
 Authorize a card transaction. This returns an authorization code and reserves funds for the merchant. Authorized transactions aren't flagged for settlement until [captured](/developers/api-reference/moneyin/capture-an-authorized-transaction).
+
 Only card transactions can be authorized. This endpoint can't be used for ACH transactions.
-<Tip>
-  Consider migrating to the [v2 Authorize endpoint](/developers/api-reference/moneyinV2/authorize-a-transaction) to take advantage of unified response codes and improved response consistency.
-</Tip>
 </dd>
 </dl>
 </dd>
@@ -1682,7 +1685,7 @@ client.money_in.authorize(
 <dd>
 
 <Warning>
-  This endpoint is deprecated and will be sunset on November 24, 2025. Migrate to [POST `/capture/{transId}`](/developers/api-reference/moneyin/capture-an-authorized-transaction)`.
+  This endpoint is deprecated. Use [POST `/capture/{transId}`](/developers/api-reference/moneyin/capture-an-authorized-transaction) instead, which supports partial captures and service fee adjustments.
 </Warning>
 
   Capture an [authorized
@@ -1759,13 +1762,13 @@ client.money_in.capture(
 <dl>
 <dd>
 
+<Warning>
+  This endpoint is deprecated. Use it only to capture transactions originally authorized with the legacy [Authorize endpoint](/developers/api-reference/moneyin/authorize-a-transaction). New integrations should use the [Capture endpoint](/developers/api-reference/moneyinV2/capture-an-authorized-transaction), which only works on transactions authorized with the current [Authorize endpoint](/developers/api-reference/moneyinV2/authorize-a-transaction).
+</Warning>
+
 Capture an [authorized transaction](/developers/api-reference/moneyin/authorize-a-transaction) to complete the transaction and move funds from the customer to merchant account.
 
 You can use this endpoint to capture both full and partial amounts of the original authorized transaction. See [Capture an authorized transaction](/developers/developer-guides/pay-in-auth-and-capture) for more information about this endpoint.
-
-<Tip>
-Consider migrating to the [v2 Capture endpoint](/developers/api-reference/moneyinV2/capture-an-authorized-transaction) to take advantage of unified response codes and improved response consistency.
-</Tip>
 </dd>
 </dl>
 </dd>
@@ -2065,11 +2068,11 @@ client.money_in.details(trans_id: "45-as456777hhhhhhhhhh77777777-324")
 <dl>
 <dd>
 
-Make a single transaction. This method authorizes and captures a payment in one step.
+<Warning>
+  This endpoint is deprecated. New integrations should use the [Make a transaction endpoint](/developers/api-reference/moneyinV2/make-a-transaction) and manage the resulting transaction with the corresponding void or refund endpoints. Transactions created with this legacy endpoint must be managed with the legacy lifecycle endpoints — they aren't interchangeable with the current ones.
+</Warning>
 
-  <Tip>
-  Consider migrating to the [v2 Make a transaction endpoint](/developers/api-reference/moneyinV2/make-a-transaction) to take advantage of unified response codes and improved response consistency.
-  </Tip>
+Make a single transaction. This method authorizes and captures a payment in one step.
 </dd>
 </dl>
 </dd>
@@ -2190,7 +2193,11 @@ client.money_in.getpaid(
 <dl>
 <dd>
 
-A reversal either refunds or voids a transaction independent of the transaction's settlement status. Send a reversal request for a transaction, and Payabli automatically determines whether it's a refund or void. You don't need to know whether the transaction is settled or not. This endpoint only works on transactions made with the v1 API. For v2 transactions, check the transaction's settlement status and call v2 void or v2 refund based on the result.
+<Warning>
+  This endpoint is deprecated and only works on transactions created with the legacy endpoints. There's no equivalent in the current endpoints. For transactions created with [Make a transaction](/developers/api-reference/moneyinV2/make-a-transaction) or [Authorize](/developers/api-reference/moneyinV2/authorize-a-transaction), check the transaction's settlement status and call [Void](/developers/api-reference/moneyinV2/void-a-transaction) or [Refund](/developers/api-reference/moneyinV2/refund-a-settled-transaction) based on the result.
+</Warning>
+
+A reversal either refunds or voids a transaction independent of the transaction's settlement status. Send a reversal request for a transaction, and Payabli automatically determines whether it's a refund or void. You don't need to know whether the transaction is settled or not. This endpoint only works on transactions made with the legacy endpoints. For transactions made with the current endpoints, check the transaction's settlement status and call void or refund based on the result.
 </dd>
 </dl>
 </dd>
@@ -2206,8 +2213,8 @@ A reversal either refunds or voids a transaction independent of the transaction'
 
 ```ruby
 client.money_in.reverse(
-  amount: 0,
-  trans_id: "10-3ffa27df-b171-44e0-b251-e95fbfc7a723"
+  trans_id: "10-3ffa27df-b171-44e0-b251-e95fbfc7a723",
+  amount: 0
 )
 ```
 </dd>
@@ -2269,11 +2276,11 @@ An amount equal to zero will refunds the total amount authorized minus any servi
 <dl>
 <dd>
 
-Refund a transaction that has settled and send money back to the account holder. If a transaction hasn't been settled, void it instead.
+<Warning>
+  This endpoint is deprecated. Use it only to refund transactions originally created with the legacy endpoints. New integrations should use the [Refund endpoint](/developers/api-reference/moneyinV2/refund-a-settled-transaction), which only works on transactions created with [Make a transaction](/developers/api-reference/moneyinV2/make-a-transaction) or [Authorize](/developers/api-reference/moneyinV2/authorize-a-transaction).
+</Warning>
 
-  <Tip>
-  Consider migrating to the [v2 Refund endpoint](/developers/api-reference/moneyinV2/refund-a-settled-transaction) to take advantage of unified response codes and improved response consistency.
-  </Tip>
+Refund a transaction that has settled and send money back to the account holder. If a transaction hasn't been settled, void it instead.
 </dd>
 </dl>
 </dd>
@@ -2289,8 +2296,8 @@ Refund a transaction that has settled and send money back to the account holder.
 
 ```ruby
 client.money_in.refund(
-  amount: 0,
-  trans_id: "10-3ffa27df-b171-44e0-b251-e95fbfc7a723"
+  trans_id: "10-3ffa27df-b171-44e0-b251-e95fbfc7a723",
+  amount: 0
 )
 ```
 </dd>
@@ -2352,6 +2359,10 @@ An amount equal to zero will refund the total amount authorized minus any servic
 <dl>
 <dd>
 
+<Warning>
+  This endpoint is deprecated. Use it only to refund transactions originally created with the legacy endpoints. To refund a split-funded transaction created with [Make a transaction](/developers/api-reference/moneyinV2/make-a-transaction) or [Authorize](/developers/api-reference/moneyinV2/authorize-a-transaction), use the [Refund endpoint](/developers/api-reference/moneyinV2/refund-a-settled-transaction) with split instructions in the request body.
+</Warning>
+
 Refunds a settled transaction with split instructions.
 </dd>
 </dl>
@@ -2370,9 +2381,8 @@ Refunds a settled transaction with split instructions.
 client.money_in.refund_with_instructions(
   trans_id: "10-3ffa27df-b171-44e0-b251-e95fbfc7a723",
   idempotency_key: "8A29FC40-CA47-1067-B31D-00DD010662DB",
-  source: "api",
-  order_description: "Materials deposit",
   amount: 100,
+  order_description: "Materials deposit",
   refund_details: {
     split_refunding: [{
       origination_entry_point: "7f1a381696",
@@ -2385,7 +2395,8 @@ client.money_in.refund_with_instructions(
       description: "Refunding deposit for undelivered materials",
       amount: 40
     }]
-  }
+  },
+  source: "api"
 )
 ```
 </dd>
@@ -2746,11 +2757,11 @@ client.money_in.validate(
 <dl>
 <dd>
 
-Cancel a transaction that hasn't been settled yet. Voiding non-captured authorizations prevents future captures. If a transaction has been settled, refund it instead.
+<Warning>
+  This endpoint is deprecated. Use it only to void transactions originally created with the legacy endpoints. New integrations should use the [Void endpoint](/developers/api-reference/moneyinV2/void-a-transaction), which only works on transactions created with [Make a transaction](/developers/api-reference/moneyinV2/make-a-transaction) or [Authorize](/developers/api-reference/moneyinV2/authorize-a-transaction).
+</Warning>
 
-  <Tip>
-  Consider migrating to the [v2 Void endpoint](/developers/api-reference/moneyinV2/void-a-transaction) to take advantage of unified response codes and improved response consistency.
-  </Tip>
+Cancel a transaction that hasn't been settled yet. Voiding non-captured authorizations prevents future captures. If a transaction has been settled, refund it instead.
 </dd>
 </dl>
 </dd>
@@ -3088,7 +3099,7 @@ client.money_in.capturev_2(
 </dl>
 </details>
 
-<details><summary><code>client.money_in.<a href="/lib/payabli/money_in/client.rb">refundv_2</a>(trans_id) -> Payabli::Types::V2TransactionResponseWrapper</code></summary>
+<details><summary><code>client.money_in.<a href="/lib/payabli/money_in/client.rb">refundv_2</a>(trans_id, request) -> Payabli::Types::V2TransactionResponseWrapper</code></summary>
 <dl>
 <dd>
 
@@ -3100,9 +3111,13 @@ client.money_in.capturev_2(
 <dl>
 <dd>
 
-Give a full refund for a transaction that has settled and send money back to the account holder. To perform a partial refund, see [Partially refund a transaction](developers/api-reference/moneyinV2/partial-refund-a-settled-transaction).
+Give a full refund for a transaction that has settled and send money back to the account holder. To perform a partial refund, see [Partially refund a transaction](/developers/api-reference/moneyinV2/partial-refund-a-settled-transaction).
 
 This is the v2 version of the refund endpoint, and returns the unified response format. See [Pay In unified response codes reference](/guides/pay-in-unified-response-codes-reference) for more information.
+
+<Note>
+  To refund a split-funded transaction, include split instructions in the request body. Omit the body for a standard refund.
+</Note>
 </dd>
 </dl>
 </dd>
@@ -3140,6 +3155,14 @@ client.money_in.refundv_2(trans_id: "10-3ffa27df-b171-44e0-b251-e95fbfc7a723")
 <dl>
 <dd>
 
+**request:** `Payabli::Types::RefundV2Request` 
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
 **request_options:** `Payabli::MoneyIn::RequestOptions` 
     
 </dd>
@@ -3152,7 +3175,7 @@ client.money_in.refundv_2(trans_id: "10-3ffa27df-b171-44e0-b251-e95fbfc7a723")
 </dl>
 </details>
 
-<details><summary><code>client.money_in.<a href="/lib/payabli/money_in/client.rb">refundv_2_amount</a>(trans_id, amount) -> Payabli::Types::V2TransactionResponseWrapper</code></summary>
+<details><summary><code>client.money_in.<a href="/lib/payabli/money_in/client.rb">refundv_2_amount</a>(trans_id, amount, request) -> Payabli::Types::V2TransactionResponseWrapper</code></summary>
 <dl>
 <dd>
 
@@ -3164,9 +3187,13 @@ client.money_in.refundv_2(trans_id: "10-3ffa27df-b171-44e0-b251-e95fbfc7a723")
 <dl>
 <dd>
 
-Refund a transaction that has settled and send money back to the account holder. If `amount` is omitted or set to 0, performs a full refund. When a non-zero `amount` is provided, this endpoint performs a partial refund.
+Refund a transaction that has settled and send money back to the account holder. If `amount` is set to 0, performs a full refund. When a non-zero `amount` is provided, this endpoint performs a partial refund.
 
 This is the v2 version of the refund endpoint, and returns the unified response format. See [Pay In unified response codes reference](/guides/pay-in-unified-response-codes-reference) for more information.
+
+<Note>
+  To refund a split-funded transaction, include split instructions in the request body. Omit the body for a standard refund.
+</Note>
 </dd>
 </dl>
 </dd>
@@ -3207,7 +3234,15 @@ client.money_in.refundv_2_amount(
 <dl>
 <dd>
 
-**amount:** `Integer` — Amount to refund from original transaction, minus any service fees charged on the original transaction. If omitted or set to 0, performs a full refund.
+**amount:** `Integer` — Amount to refund from original transaction, minus any service fees charged on the original transaction. If set to 0, performs a full refund.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request:** `Payabli::Types::RefundV2Request` 
     
 </dd>
 </dl>
@@ -3285,6 +3320,96 @@ client.money_in.voidv_2(trans_id: "10-3ffa27df-b171-44e0-b251-e95fbfc7a723")
 </dl>
 
 
+</dd>
+</dl>
+</details>
+
+## Token
+<details><summary><code>client.token.<a href="/lib/payabli/token/client.rb">create_server_side_token</a>(request) -> Payabli::Types::PayabliAccessTokenResponse</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Exchanges a client ID and client secret for a short-lived Bearer access token using the OAuth2 client-credentials flow. Designed for server-to-server use: the credentials and the returned token stay on your backend. Send the returned `access_token` in the `Authorization` header as `Bearer <access_token>` on subsequent API calls. See the [OAuth authentication guide](/developers/oauth-authentication) for the full flow.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.token.create_server_side_token(
+  client_id: "YOUR_CLIENT_ID",
+  client_secret: "YOUR_CLIENT_SECRET"
+)
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**client_id:** `String` — The client ID issued for your integration when credentials are provisioned in the Payabli Portal.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**client_secret:** `String` — The client secret issued alongside the client ID. Keep it on your backend and never expose it in client-side code.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**state:** `String` — An optional opaque value echoed back in the response. Use it to correlate the request with its response.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**permissions:** `Internal::Types::Array[String]` — An optional array of permission IDs that scopes the token to a subset of the credential's granted permissions. When omitted, the token carries all permissions granted to the credential.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Payabli::Token::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
 </dd>
 </dl>
 </details>
@@ -3541,7 +3666,7 @@ client.subscription.new_subscription(
   },
   payment_method: {
     cardcvv: "123",
-    cardexp: "02/25",
+    cardexp: "12/29",
     card_holder: "John Cassian",
     cardnumber: "4111111111111111",
     cardzip: "37615",
@@ -3908,8 +4033,8 @@ Deletes a file attached to an invoice.
 
 ```ruby
 client.invoice.delete_attached_from_invoice(
-  filename: "0_Bill.pdf",
-  id_invoice: 23548884
+  id_invoice: 23548884,
+  filename: "0_Bill.pdf"
 )
 ```
 </dd>
@@ -4734,6 +4859,8 @@ client.invoice.get_invoice_pdf(id_invoice: 23548884)
 <dd>
 
 Generates a payment link for an invoice from the invoice ID.
+
+The payment page configuration blocks (`logo`, `page`, `paymentMethods`, `review`, `messageBeforePaying`, `paymentButton`, `notes`, `contactUs`, and `settings`) are optional. When you omit a block, Payabli applies a default rather than hiding it. The block is enabled at a fixed display order, so the generated page stays complete and branded. To hide a section, send the block explicitly with `enabled` set to `false`. An explicit value is always honored and is never replaced by a default. For each block's default, see its description in the request body.
 </dd>
 </dl>
 </dd>
@@ -4903,7 +5030,7 @@ client.payment_link.add_pay_link_from_invoice(
 <dl>
 <dd>
 
-**contact_us:** `Payabli::Types::ContactElement` — ContactUs section of payment link page
+**contact_us:** `Payabli::Types::ContactElement` — Contact us section of payment link page. If omitted, this block is enabled at display order 11.
     
 </dd>
 </dl>
@@ -4911,7 +5038,7 @@ client.payment_link.add_pay_link_from_invoice(
 <dl>
 <dd>
 
-**invoices:** `Payabli::Types::InvoiceElement` — Invoices section of payment link page
+**invoices:** `Payabli::Types::InvoiceElement` — Invoices section of payment link page. Required. Omitting it returns a `400` error with code `7045`.
     
 </dd>
 </dl>
@@ -4919,7 +5046,7 @@ client.payment_link.add_pay_link_from_invoice(
 <dl>
 <dd>
 
-**logo:** `Payabli::Types::Element` — Logo section of payment link page
+**logo:** `Payabli::Types::Element` — Logo section of payment link page. If omitted, this block is enabled at display order 1, and the logo image is resolved from the paypoint's entry logo.
     
 </dd>
 </dl>
@@ -4927,7 +5054,7 @@ client.payment_link.add_pay_link_from_invoice(
 <dl>
 <dd>
 
-**message_before_paying:** `Payabli::Types::LabelElement` — Message section of payment link page
+**message_before_paying:** `Payabli::Types::LabelElement` — Message section of payment link page. If omitted, this block is enabled at display order 5.
     
 </dd>
 </dl>
@@ -4935,7 +5062,7 @@ client.payment_link.add_pay_link_from_invoice(
 <dl>
 <dd>
 
-**notes:** `Payabli::Types::NoteElement` — Notes section of payment link page
+**notes:** `Payabli::Types::NoteElement` — Notes section of payment link page. If omitted, this block is enabled at display order 10.
     
 </dd>
 </dl>
@@ -4943,7 +5070,7 @@ client.payment_link.add_pay_link_from_invoice(
 <dl>
 <dd>
 
-**page:** `Payabli::Types::PageElement` — Page header section of payment link page
+**page:** `Payabli::Types::PageElement` — Page header section of payment link page. If omitted, this block is enabled at display order 2.
     
 </dd>
 </dl>
@@ -4951,7 +5078,7 @@ client.payment_link.add_pay_link_from_invoice(
 <dl>
 <dd>
 
-**payment_button:** `Payabli::Types::LabelElement` — Payment button section of payment link page
+**payment_button:** `Payabli::Types::LabelElement` — Payment button section of payment link page. If omitted, this block is enabled at display order 6, with the label "Pay Now".
     
 </dd>
 </dl>
@@ -4959,7 +5086,7 @@ client.payment_link.add_pay_link_from_invoice(
 <dl>
 <dd>
 
-**payment_methods:** `Payabli::Types::MethodElement` — Payment methods section of payment link page
+**payment_methods:** `Payabli::Types::MethodElement` — Payment methods section of payment link page. If omitted, this block is enabled at display order 3, with all payment methods enabled except RDC.
     
 </dd>
 </dl>
@@ -4975,7 +5102,7 @@ client.payment_link.add_pay_link_from_invoice(
 <dl>
 <dd>
 
-**review:** `Payabli::Types::HeaderElement` — Review section of payment link page
+**review:** `Payabli::Types::HeaderElement` — Review section of payment link page. If omitted, this block is enabled at display order 4.
     
 </dd>
 </dl>
@@ -4983,7 +5110,7 @@ client.payment_link.add_pay_link_from_invoice(
 <dl>
 <dd>
 
-**settings:** `Payabli::Types::PagelinkSetting` — Settings section of payment link page
+**settings:** `Payabli::Types::PagelinkSetting` — Settings section of payment link page. If omitted, defaults are applied, including page color `#10a0e3` and language `en`.
     
 </dd>
 </dl>
@@ -6075,7 +6202,7 @@ client.token_storage.add_method(
   method_description: "Primary Visa card",
   payment_method: {
     cardcvv: "123",
-    cardexp: "02/25",
+    cardexp: "12/29",
     card_holder: "John Doe",
     cardnumber: "4111111111111111",
     cardzip: "12345",
@@ -6285,7 +6412,7 @@ client.token_storage.update_method(
   fallback_auth: true,
   payment_method: {
     cardcvv: "123",
-    cardexp: "02/25",
+    cardexp: "12/29",
     card_holder: "John Doe",
     cardnumber: "4111111111111111",
     cardzip: "12345",
@@ -7231,15 +7358,15 @@ Add a payment method domain to an organization or paypoint.
 
 ```ruby
 client.payment_method_domain.add_payment_method_domain(
-  domain_name: "checkout.example.com",
-  entity_id: 109,
-  entity_type: "paypoint",
   apple_pay: {
     is_enabled: true
   },
   google_pay: {
     is_enabled: true
-  }
+  },
+  domain_name: "checkout.example.com",
+  entity_id: 109,
+  entity_type: "paypoint"
 )
 ```
 </dd>
@@ -12460,6 +12587,7 @@ See [Filters and Conditions Reference](/developers/developer-guides/pay-ops-repo
 - `payaccountLastfour` (nct, ct)
 - `payaccountType` (ne, eq, in, nin)
 - `payaccountCurrency` (ne, eq, in, nin)
+- `binCardType` (eq, ne, in, nin). Filters by card type for card transactions. Accepts `CREDIT`, `DEBIT`, or `PREPAID`. Case-insensitive.
 - `customerFirstname` (ct, nct, eq, ne)
 - `customerLastname` (ct, nct, eq, ne)
 - `customerName` (ct, nct)
@@ -12660,6 +12788,7 @@ See [Filters and Conditions Reference](/developers/developer-guides/pay-ops-repo
 - `payaccountLastfour` (nct, ct)
 - `payaccountType` (ne, eq, in, nin)
 - `payaccountCurrency` (ne, eq, in, nin)
+- `binCardType` (eq, ne, in, nin). Filters by card type for card transactions. Accepts `CREDIT`, `DEBIT`, or `PREPAID`. Case-insensitive.
 - `customerFirstname` (ct, nct, eq, ne)
 - `customerLastname` (ct, nct, eq, ne)
 - `customerName` (ct, nct)
@@ -13254,6 +13383,8 @@ List of field names accepted:
   - `paypointDbaName` (ne, eq, ct, nct)
   - `batchNumber` (ne, eq, ct, nct)
   - `batchId` (ne, eq, in, nin)
+  - `detailType` (eq, ne, in, nin, ct, nct)
+  - `detailMethod` (eq, ne, in, nin, ct, nct)
     
 </dd>
 </dl>
@@ -13381,6 +13512,8 @@ List of field names accepted:
   - `paypointDbaName` (ne, eq, ct, nct)
   - `batchNumber` (ne, eq, ct, nct)
   - `batchId` (ne, eq, in, nin)
+  - `detailType` (eq, ne, in, nin, ct, nct)
+  - `detailMethod` (eq, ne, in, nin, ct, nct)
     
 </dd>
 </dl>
@@ -14950,9 +15083,9 @@ client.notificationlogs.search_notification_logs(
   page_size: 20,
   start_date: "2024-01-01T00:00:00Z",
   end_date: "2024-01-31T23:59:59Z",
-  org_id: 123,
   notification_event: "ActivatedMerchant",
-  succeeded: true
+  succeeded: true,
+  org_id: 123
 )
 ```
 </dd>
@@ -15266,8 +15399,8 @@ Register a cloud device to an entrypoint. See [Devices Quickstart](/developers/d
 ```ruby
 client.cloud.add_device(
   entry: "8cfec329267",
-  registration_code: "YS7DS5",
-  description: "Front Desk POS"
+  description: "Front Desk POS",
+  registration_code: "YS7DS5"
 )
 ```
 </dd>
@@ -15361,8 +15494,8 @@ Remove a cloud device from an entrypoint.
 
 ```ruby
 client.cloud.remove_device(
-  device_id: "499585-389fj484-3jcj8hj3",
-  entry: "8cfec329267"
+  entry: "8cfec329267",
+  device_id: "499585-389fj484-3jcj8hj3"
 )
 ```
 </dd>
@@ -15434,8 +15567,8 @@ Retrieve the registration history for a device.
 
 ```ruby
 client.cloud.history_device(
-  device_id: "499585-389fj484-3jcj8hj3",
-  entry: "8cfec329267"
+  entry: "8cfec329267",
+  device_id: "499585-389fj484-3jcj8hj3"
 )
 ```
 </dd>
@@ -16556,7 +16689,7 @@ client.boarding.get_by_template_id_link_application(template_id: 80)
 <dl>
 <dd>
 
-**template_id:** `Integer` — The boarding template ID. You can find this at the end of the boarding template URL in PartnerHub. Example: `https://partner-sandbox.payabli.com/myorganization/boarding/edittemplate/80`. Here, the template ID is `80`.
+**template_id:** `Integer` — The boarding template ID. You can find this at the end of the boarding template URL in the Payabli Portal. Example: `https://partner-sandbox.payabli.com/myorganization/boarding/edittemplate/80`. Here, the template ID is `80`.
     
 </dd>
 </dl>
@@ -17198,7 +17331,7 @@ client.templates.delete_template(template_id: 80)
 <dl>
 <dd>
 
-**template_id:** `Integer` — The boarding template ID. You can find this at the end of the boarding template URL in PartnerHub. Example: `https://partner-sandbox.payabli.com/myorganization/boarding/edittemplate/80`. Here, the template ID is `80`.
+**template_id:** `Integer` — The boarding template ID. You can find this at the end of the boarding template URL in the Payabli Portal. Example: `https://partner-sandbox.payabli.com/myorganization/boarding/edittemplate/80`. Here, the template ID is `80`.
     
 </dd>
 </dl>
@@ -17246,8 +17379,8 @@ Generates a boarding link from a boarding template.
 
 ```ruby
 client.templates.getlink_template(
-  ignore_empty: true,
-  template_id: 80
+  template_id: 80,
+  ignore_empty: true
 )
 ```
 </dd>
@@ -17263,7 +17396,7 @@ client.templates.getlink_template(
 <dl>
 <dd>
 
-**template_id:** `Integer` — The boarding template ID. You can find this at the end of the boarding template URL in PartnerHub. Example: `https://partner-sandbox.payabli.com/myorganization/boarding/edittemplate/80`. Here, the template ID is `80`.
+**template_id:** `Integer` — The boarding template ID. You can find this at the end of the boarding template URL in the Payabli Portal. Example: `https://partner-sandbox.payabli.com/myorganization/boarding/edittemplate/80`. Here, the template ID is `80`.
     
 </dd>
 </dl>
@@ -17333,7 +17466,7 @@ client.templates.get_template(template_id: 80)
 <dl>
 <dd>
 
-**template_id:** `Integer` — The boarding template ID. You can find this at the end of the boarding template URL in PartnerHub. Example: `https://partner-sandbox.payabli.com/myorganization/boarding/edittemplate/80`. Here, the template ID is `80`.
+**template_id:** `Integer` — The boarding template ID. You can find this at the end of the boarding template URL in the Payabli Portal. Example: `https://partner-sandbox.payabli.com/myorganization/boarding/edittemplate/80`. Here, the template ID is `80`.
     
 </dd>
 </dl>
@@ -17694,8 +17827,8 @@ Export batch details for a paypoint. Use filters to limit results.
 
 ```ruby
 client.export.export_batch_details(
-  entry: "8cfec329267",
   format: "csv",
+  entry: "8cfec329267",
   columns_export: "BatchDate:Batch_Date,PaypointName:Legal_name",
   from_record: 251,
   limit_record: 1000
@@ -18046,8 +18179,8 @@ Export a list of batches for an entrypoint. Use filters to limit results.
 
 ```ruby
 client.export.export_batches(
-  entry: "8cfec329267",
   format: "csv",
+  entry: "8cfec329267",
   columns_export: "BatchDate:Batch_Date,PaypointName:Legal_name",
   from_record: 251,
   limit_record: 1000
@@ -18376,8 +18509,8 @@ Export a list of money out batches for a paypoint. Use filters to limit results.
 
 ```ruby
 client.export.export_batches_out(
-  entry: "8cfec329267",
   format: "csv",
+  entry: "8cfec329267",
   columns_export: "BatchDate:Batch_Date,PaypointName:Legal_name",
   from_record: 251,
   limit_record: 1000
@@ -18668,8 +18801,8 @@ Export a list of bills for an entrypoint. Use filters to limit results.
 
 ```ruby
 client.export.export_bills(
-  entry: "8cfec329267",
   format: "csv",
+  entry: "8cfec329267",
   columns_export: "BatchDate:Batch_Date,PaypointName:Legal_name",
   from_record: 251,
   limit_record: 1000
@@ -18996,8 +19129,8 @@ Export a list of chargebacks and ACH returns for an entrypoint. Use filters to l
 
 ```ruby
 client.export.export_chargebacks(
-  entry: "8cfec329267",
   format: "csv",
+  entry: "8cfec329267",
   columns_export: "BatchDate:Batch_Date,PaypointName:Legal_name",
   from_record: 251,
   limit_record: 1000
@@ -19366,8 +19499,8 @@ Export a list of customers for an entrypoint. Use filters to limit results.
 
 ```ruby
 client.export.export_customers(
-  entry: "8cfec329267",
   format: "csv",
+  entry: "8cfec329267",
   columns_export: "BatchDate:Batch_Date,PaypointName:Legal_name",
   from_record: 251,
   limit_record: 1000
@@ -19722,8 +19855,8 @@ Export list of invoices for an entrypoint. Use filters to limit results.
 
 ```ruby
 client.export.export_invoices(
-  entry: "8cfec329267",
   format: "csv",
+  entry: "8cfec329267",
   columns_export: "BatchDate:Batch_Date,PaypointName:Legal_name",
   from_record: 251,
   limit_record: 1000
@@ -20261,8 +20394,8 @@ Export a list of payouts and their statuses for an entrypoint. Use filters to li
 
 ```ruby
 client.export.export_payout(
-  entry: "8cfec329267",
   format: "csv",
+  entry: "8cfec329267",
   columns_export: "BatchDate:Batch_Date,PaypointName:Legal_name",
   from_record: 251,
   limit_record: 1000
@@ -20749,8 +20882,8 @@ Export a list of settled transactions for an entrypoint. Use filters to limit re
 
 ```ruby
 client.export.export_settlements(
-  entry: "8cfec329267",
   format: "csv",
+  entry: "8cfec329267",
   columns_export: "BatchDate:Batch_Date,PaypointName:Legal_name",
   from_record: 251,
   limit_record: 1000
@@ -21117,8 +21250,8 @@ Export a list of subscriptions for an entrypoint. Use filters to limit results.
 
 ```ruby
 client.export.export_subscriptions(
-  entry: "8cfec329267",
   format: "csv",
+  entry: "8cfec329267",
   columns_export: "BatchDate:Batch_Date,PaypointName:Legal_name",
   from_record: 251,
   limit_record: 1000
@@ -21489,8 +21622,8 @@ Export a list of transactions for an entrypoint in a file in XLSX or CSV format.
 
 ```ruby
 client.export.export_transactions(
-  entry: "8cfec329267",
   format: "csv",
+  entry: "8cfec329267",
   columns_export: "BatchDate:Batch_Date,PaypointName:Legal_name",
   from_record: 251,
   limit_record: 1000
@@ -21869,8 +22002,8 @@ Export a list of transfer details for an entrypoint. Use filters to limit result
 
 ```ruby
 client.export.export_transfer_details(
-  entry: "8cfec329267",
   format: "csv",
+  entry: "8cfec329267",
   transfer_id: 4521,
   columns_export: "BatchDate:Batch_Date,PaypointName:Legal_name",
   from_record: 251,
@@ -22196,8 +22329,8 @@ Export a list of vendors for an entrypoint. Use filters to limit results.
 
 ```ruby
 client.export.export_vendors(
-  entry: "8cfec329267",
   format: "csv",
+  entry: "8cfec329267",
   columns_export: "BatchDate:Batch_Date,PaypointName:Legal_name",
   from_record: 251,
   limit_record: 1000
@@ -23448,12 +23581,12 @@ Retrieves the basic statistics for an organization or a paypoint, for a given ti
 
 ```ruby
 client.statistic.basic_stats(
-  entry_id: 1000000,
+  mode: "custom",
   freq: "m",
   level: 2,
-  mode: "custom",
-  start_date: "2025-11-01",
-  end_date: "2025-11-30"
+  entry_id: 1000000,
+  end_date: "2025-11-30",
+  start_date: "2025-11-01"
 )
 ```
 </dd>
@@ -23607,9 +23740,9 @@ Retrieves the basic statistics for a customer for a specific time period, groupe
 
 ```ruby
 client.statistic.customer_basic_stats(
-  customer_id: 4440,
+  mode: "ytd",
   freq: "m",
-  mode: "ytd"
+  customer_id: 4440
 )
 ```
 </dd>
@@ -23664,7 +23797,7 @@ For example, `w` groups the results by week.
 <dl>
 <dd>
 
-**customer_id:** `Integer` — Payabli-generated customer ID. Maps to "Customer ID" column in PartnerHub.
+**customer_id:** `Integer` — Payabli-generated customer ID. Maps to "Customer ID" column in the Payabli Portal.
     
 </dd>
 </dl>
@@ -23720,9 +23853,9 @@ Retrieves the subscription statistics for a given interval for a paypoint or org
 
 ```ruby
 client.statistic.sub_stats(
-  entry_id: 1000000,
   interval: "30",
-  level: 2
+  level: 2,
+  entry_id: 1000000
 )
 ```
 </dd>
@@ -23822,9 +23955,9 @@ Retrieve the basic statistics about a vendor for a given time period, grouped by
 
 ```ruby
 client.statistic.vendor_basic_stats(
+  mode: "ytd",
   freq: "m",
-  id_vendor: 1,
-  mode: "ytd"
+  id_vendor: 1
 )
 ```
 </dd>
@@ -25049,9 +25182,9 @@ Resends the MFA code to the user via the selected MFA mode (email or SMS).
 
 ```ruby
 client.user.resend_mfa_code(
+  usrname: "usrname",
   entry: "8cfec329267",
-  entry_type: 1,
-  usrname: "usrname"
+  entry_type: 1
 )
 ```
 </dd>
@@ -25447,12 +25580,12 @@ client.vendor.enrich_vendor(
   vendor_id: 456,
   scope: ["invoice_scan"],
   apply_enrichment_data: false,
-  fallback_method: "check",
   invoice_file: {
     ftype: "pdf",
     filename: "invoice-2026-001.pdf",
     f_content: "<base64-encoded-pdf>"
-  }
+  },
+  fallback_method: "check"
 )
 ```
 </dd>
@@ -25500,7 +25633,7 @@ client.vendor.enrich_vendor(
 <dl>
 <dd>
 
-**schedule_call_if_needed:** `Internal::Types::Boolean` — When `true`, triggers an AI outreach call if enrichment stages return insufficient payment acceptance info. This feature is currently in development.
+**schedule_call_if_needed:** `Internal::Types::Boolean` — When `true`, Payabli schedules an AI outreach call to the vendor if the enrichment stages return insufficient payment acceptance info. The call collects the vendor's preferred payment method and contact email. This is the third enrichment stage and is opt-in at the org level. See the schedule outreach call endpoint for behavior and requirements.
     
 </dd>
 </dl>
@@ -25544,8 +25677,7 @@ client.vendor.enrich_vendor(
 </dl>
 </details>
 
-## GhostCard
-<details><summary><code>client.ghost_card.<a href="/lib/payabli/ghost_card/client.rb">create_ghost_card</a>(entry, request) -> Payabli::Types::CreateGhostCardResponse</code></summary>
+<details><summary><code>client.vendor.<a href="/lib/payabli/vendor/client.rb">schedule_enrichment_call</a>(entry, request) -> Payabli::Types::VendorScheduleCallResponse</code></summary>
 <dl>
 <dd>
 
@@ -25557,11 +25689,7 @@ client.vendor.enrich_vendor(
 <dl>
 <dd>
 
-Creates a ghost card, a multi-use virtual debit card issued to a vendor for recurring or discretionary spend.
-
-Unlike single-use virtual cards issued as part of a payout transaction, ghost cards aren't tied to a specific payout. They're issued directly to a vendor and can be reused up to a configurable number of times within the card's spending limits.
-
-Only one ghost card can exist per vendor per paypoint. To issue a new card to the same vendor, cancel the existing card first.
+Schedules an AI outreach call to a vendor to collect their preferred payment method and contact email. This is the third enrichment stage. Calls are scheduled for the next business day at around 9 AM in the vendor's timezone, with retries on no-answer and a fallback payment method applied when retries are exhausted. This feature is opt-in at the org level. Contact your Payabli representative to enable it, provision a phone number, and discuss pricing.
 </dd>
 </dl>
 </dd>
@@ -25576,23 +25704,15 @@ Only one ghost card can exist per vendor per paypoint. To issue a new card to th
 <dd>
 
 ```ruby
-client.ghost_card.create_ghost_card(
+client.vendor.schedule_enrichment_call(
   entry: "8cfec329267",
   vendor_id: 456,
-  expense_limit: 500,
-  amount: 500,
-  max_number_of_uses: 3,
-  exact_amount: false,
-  expense_limit_period: "monthly",
-  billing_cycle: "monthly",
-  billing_cycle_day: "1",
-  daily_transaction_count: 5,
-  daily_amount_limit: 200,
-  transaction_amount_limit: 100,
-  mcc: "5411",
-  tcc: "R",
-  misc_1: "PO-98765",
-  misc_2: "Dept-Finance"
+  phone: "5555550200",
+  enrichment_id: "enrich-3890-a1b2c3d4",
+  bill_id: 54323,
+  fallback_method: "check",
+  max_retries: 3,
+  timezone: "America/New_York"
 )
 ```
 </dd>
@@ -25608,7 +25728,7 @@ client.ghost_card.create_ghost_card(
 <dl>
 <dd>
 
-**entry:** `String` — The entity's entrypoint identifier. [Learn more](/developers/api-reference/api-overview#entrypoint-vs-entry)
+**entry:** `String` — Entrypoint identifier.
     
 </dd>
 </dl>
@@ -25616,7 +25736,7 @@ client.ghost_card.create_ghost_card(
 <dl>
 <dd>
 
-**vendor_id:** `Integer` — ID of the vendor who receives the card. The vendor must belong to the paypoint and have an active status.
+**vendor_id:** `Integer` — ID of the vendor to call. Must be active and belong to the entrypoint in the path.
     
 </dd>
 </dl>
@@ -25624,7 +25744,7 @@ client.ghost_card.create_ghost_card(
 <dl>
 <dd>
 
-**expense_limit:** `Integer` — Spending limit for the card. Must be greater than `0` and can't exceed the paypoint's configured payout credit limit.
+**phone:** `String` — Vendor phone number to call, digits only. Optional. When omitted, Payabli uses the phone number on the vendor's record. If the vendor has no phone on record, the request returns an error.
     
 </dd>
 </dl>
@@ -25632,7 +25752,7 @@ client.ghost_card.create_ghost_card(
 <dl>
 <dd>
 
-**expiration_date:** `String` — Requested expiration date for the card. If not provided, defaults to 30 days from creation.
+**enrichment_id:** `String` — ID of the originating enrichment run to associate with this call. Optional. When omitted, Payabli generates a standalone call schedule and skips the enrichment lookup. The bill due-date check only runs when both `enrichmentId` and `billId` are supplied.
     
 </dd>
 </dl>
@@ -25640,7 +25760,7 @@ client.ghost_card.create_ghost_card(
 <dl>
 <dd>
 
-**amount:** `Integer` — Initial load amount for the card.
+**bill_id:** `Integer` — Bill ID used for the due-date check. When the bill is due in fewer than three days, the call is skipped and the fallback method is applied. Only evaluated when `enrichmentId` is also supplied.
     
 </dd>
 </dl>
@@ -25648,7 +25768,7 @@ client.ghost_card.create_ghost_card(
 <dl>
 <dd>
 
-**max_number_of_uses:** `Integer` — Maximum number of times the card can be used. Ignored and set to `1` when `exactAmount` is `true`.
+**fallback_method:** `String` — Payment method to apply to the vendor record if the call can't determine a preference or all retries are exhausted. Values are `check` (the default) or `managed`.
     
 </dd>
 </dl>
@@ -25656,7 +25776,7 @@ client.ghost_card.create_ghost_card(
 <dl>
 <dd>
 
-**exact_amount:** `Internal::Types::Boolean` — When `true`, restricts the card to a single use. `maxNumberOfUses` is automatically set to `1` regardless of any other value provided.
+**max_retries:** `Integer` — Number of times to retry the call if the vendor doesn't answer. Defaults to 3. Maximum is 5. The get outreach call status response reports this value as `maxAttempts`.
     
 </dd>
 </dl>
@@ -25664,7 +25784,7 @@ client.ghost_card.create_ghost_card(
 <dl>
 <dd>
 
-**expense_limit_period:** `String` — Time period over which `expenseLimit` applies (for example, `monthly` or `weekly`).
+**timezone:** `String` — IANA timezone identifier used to schedule the call in the vendor's local time. Defaults to `America/New_York`.
     
 </dd>
 </dl>
@@ -25672,7 +25792,7 @@ client.ghost_card.create_ghost_card(
 <dl>
 <dd>
 
-**billing_cycle:** `String` — Billing cycle identifier.
+**send_now:** `Internal::Types::Boolean` — When `true`, dispatches the call immediately and bypasses the business-hours window and the bill due-date check. Defaults to `false`.
     
 </dd>
 </dl>
@@ -25680,40 +25800,250 @@ client.ghost_card.create_ghost_card(
 <dl>
 <dd>
 
-**billing_cycle_day:** `String` — Day within the billing cycle.
+**request_options:** `Payabli::Vendor::RequestOptions` 
     
 </dd>
 </dl>
+</dd>
+</dl>
 
-<dl>
-<dd>
 
-**daily_transaction_count:** `Integer` — Maximum number of transactions allowed per day.
-    
 </dd>
 </dl>
+</details>
 
+<details><summary><code>client.vendor.<a href="/lib/payabli/vendor/client.rb">get_enrichment_call_status</a>(id_vendor) -> Payabli::Types::VendorCallStatusResponse</code></summary>
 <dl>
 <dd>
 
-**daily_amount_limit:** `Integer` — Maximum total spend allowed per day.
-    
-</dd>
-</dl>
+#### 📝 Description
 
 <dl>
 <dd>
 
-**transaction_amount_limit:** `Integer` — Maximum spend allowed per single transaction.
-    
-</dd>
-</dl>
-
 <dl>
 <dd>
 
-**mcc:** `String` — Merchant Category Code to restrict where the card can be used. Must be a valid MCC if provided.
-    
+Returns the latest AI outreach call activity for a vendor. The response is a composite object with a `state` discriminator (`none`, `scheduled`, `successful`, or `failed`); the block that matches the current state is populated. When the vendor has no call activity, `state` is `none` and the response returns HTTP 200.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.vendor.get_enrichment_call_status(id_vendor: 456)
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**id_vendor:** `Integer` — ID of the vendor to read call status for.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Payabli::Vendor::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</dd>
+</dl>
+</details>
+
+## GhostCard
+<details><summary><code>client.ghost_card.<a href="/lib/payabli/ghost_card/client.rb">create_ghost_card</a>(entry, request) -> Payabli::Types::CreateGhostCardResponse</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Creates a ghost card, a multi-use virtual debit card issued to a vendor for recurring or discretionary spend.
+
+Unlike single-use virtual cards issued as part of a payout transaction, ghost cards aren't tied to a specific payout. They're issued directly to a vendor and can be reused up to a configurable number of times within the card's spending limits.
+
+Only one ghost card can exist per vendor per paypoint. To issue a new card to the same vendor, cancel the existing card first.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.ghost_card.create_ghost_card(
+  entry: "8cfec329267",
+  vendor_id: 456,
+  expense_limit: 500,
+  amount: 500,
+  max_number_of_uses: 3,
+  exact_amount: false,
+  expense_limit_period: "monthly",
+  billing_cycle: "monthly",
+  billing_cycle_day: "1",
+  daily_transaction_count: 5,
+  daily_amount_limit: 200,
+  transaction_amount_limit: 100,
+  mcc: "5411",
+  tcc: "R",
+  misc_1: "PO-98765",
+  misc_2: "Dept-Finance"
+)
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**entry:** `String` — The entity's entrypoint identifier. [Learn more](/developers/api-reference/api-overview#entrypoint-vs-entry)
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**vendor_id:** `Integer` — ID of the vendor who receives the card. The vendor must belong to the paypoint and have an active status.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**expense_limit:** `Integer` — Spending limit for the card. Must be greater than `0` and can't exceed the paypoint's configured payout credit limit.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**expiration_date:** `String` — Requested expiration date for the card. If not provided, defaults to 30 days from creation.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**amount:** `Integer` — Initial load amount for the card.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**max_number_of_uses:** `Integer` — Maximum number of times the card can be used. Ignored and set to `1` when `exactAmount` is `true`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**exact_amount:** `Internal::Types::Boolean` — When `true`, restricts the card to a single use. `maxNumberOfUses` is automatically set to `1` regardless of any other value provided.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**expense_limit_period:** `String` — Time period over which `expenseLimit` applies (for example, `monthly` or `weekly`).
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**billing_cycle:** `String` — Billing cycle identifier.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**billing_cycle_day:** `String` — Day within the billing cycle.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**daily_transaction_count:** `Integer` — Maximum number of transactions allowed per day.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**daily_amount_limit:** `Integer` — Maximum total spend allowed per day.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**transaction_amount_limit:** `Integer` — Maximum spend allowed per single transaction.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**mcc:** `String` — Merchant Category Code to restrict where the card can be used. Must be a valid MCC if provided.
+    
 </dd>
 </dl>
 
@@ -25855,7 +26185,11 @@ Authorizes a transaction for payout.
 
 If you don't pass `autoCapture` with a value of `true`, authorized transactions aren't flagged for settlement until captured. Use the `referenceId` returned in the response to capture the transaction.
 
-When `autoCapture` is `true`, Payabli captures the transaction asynchronously after authorization. The response confirms only that the transaction was authorized; it doesn't confirm that capture succeeded. To confirm capture, listen for the [`payout_transaction_approvedcaptured`](/developers/webhooks/payout-transaction-approved-captured) webhook event.
+When `autoCapture` is `true`, Payabli captures the transaction asynchronously after authorization. The response confirms only that the transaction was authorized; it doesn't confirm that capture succeeded. To confirm capture, listen for the [`payout_transaction_approvedcaptured`](/developers/api-reference/webhooks-overview/payout-transaction-approved-captured) webhook event.
+
+If a velocity fraud alert is triggered, the endpoint returns a `202` response with `responseCode` `9051`, and the authorization is held for risk review rather than rejected. If a risk policy blocks the transaction, the endpoint returns a `422` response with `responseCode` `9005`, a terminal rejection.
+
+For check payouts, Payabli validates the remit (mailing) address at authorization. If the address fails deliverability validation, the endpoint returns a `422` response and doesn't charge the paypoint. Correct the address and re-authorize. Other payout rails (ACH, RTP, virtual card, wire, and managed payables) aren't affected.
 </dd>
 </dl>
 </dd>
@@ -25872,21 +26206,21 @@ When `autoCapture` is `true`, Payabli captures the transaction asynchronously af
 ```ruby
 client.money_out.authorize_out(
   entry_point: "8cfec329267",
-  auto_capture: true,
-  invoice_data: [{
-    bill_id: 54323
-  }],
   order_description: "Window Painting",
+  payment_method: {
+    method_: "managed"
+  },
   payment_details: {
     total_amount: 47,
     unbundled: false
   },
-  payment_method: {
-    method_: "managed"
-  },
   vendor_data: {
     vendor_number: "VEN-123"
-  }
+  },
+  invoice_data: [{
+    bill_id: 54323
+  }],
+  auto_capture: true
 )
 ```
 </dd>
@@ -26310,7 +26644,9 @@ client.money_out.capture_all_out(body: %w[2-29 2-28 2-27])
 <dl>
 <dd>
 
-Captures a single authorized payout transaction by ID. If the transaction was authorized with `autoCapture` set to `true`,  you don't need to call this endpoint to capture the transaction for processing.
+Captures a single authorized payout transaction by ID. If the transaction was authorized with `autoCapture` set to `true`, you don't need to call this endpoint to capture the transaction for processing.
+
+If a velocity fraud alert is triggered, the endpoint returns a `202` response with `responseCode` `9051`, and the capture is held for risk review rather than rejected. If a risk policy blocks the transaction, the endpoint returns a `422` response with `responseCode` `9005`, a terminal rejection.
 </dd>
 </dl>
 </dd>
@@ -26488,6 +26824,83 @@ client.money_out.v_card_get(card_token: "20230403315245421165")
 </dl>
 
 
+</dd>
+</dl>
+</details>
+
+<details><summary><code>client.money_out.<a href="/lib/payabli/money_out/client.rb">renew_v_card</a>(card_token, request) -> Payabli::Types::RenewVCardResponse</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Renews an expired or expiring virtual card by extending its expiration date to a future month.
+
+The card must be a virtual card that hasn't been fully used. The new expiration date must be in `MM-YYYY` or `MM/YYYY` format and no more than 2 years and 363 days in the future. The card expires on the last day of the month you specify.
+
+On success, `referenceId` holds the renewed card's token (the card processor may issue a new token). The response reuses the standard payout result object, so the payment-transaction fields it carries don't apply to renewal and always return `null`.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.money_out.renew_v_card(
+  card_token: "20231206142225226104",
+  expiration_date: "12-2027"
+)
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**card_token:** `String` — ID for the virtual card to renew.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**expiration_date:** `String` — The new expiration date for the virtual card, in `MM-YYYY` or `MM/YYYY` format. The card expires on the last day of the month you specify. The date can't be more than 2 years and 363 days in the future.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Payabli::MoneyOut::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
 </dd>
 </dl>
 </details>
@@ -26801,6 +27214,105 @@ client.money_out.reissue_out(
 </dl>
 
 
+</dd>
+</dl>
+</details>
+
+## Funding
+<details><summary><code>client.funding.<a href="/lib/payabli/funding/client.rb">deposit_funds</a>(request) -> Payabli::Types::DepositFundsResponse</code></summary>
+<dl>
+<dd>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+Deposits funds into a paypoint's available payout balance. Deposited funds enter a pending state and aren't available for instant payouts until confirmed through FBO reconciliation.
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.funding.deposit_funds(
+  amount: 10,
+  entrypoint: "48acde49",
+  account_id: "333"
+)
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**amount:** `Integer` — The amount to deposit, in dollars. Must be greater than zero.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**entrypoint:** `String` — The entry point identifier for the paypoint receiving the deposit.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**account_id:** `String` — The remittance account ID to withdraw funds from.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**paypoint_id:** `Integer` — The paypoint ID. Optional if the entry point uniquely identifies the paypoint.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**same_day_ach:** `Internal::Types::Boolean` — When `true` and the request is submitted before 2 PM ET, the deposit processes as same-day ACH. If the request is submitted after 2 PM ET, it processes as standard ACH regardless of this flag.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**request_options:** `Payabli::Funding::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
 </dd>
 </dl>
 </details>