payabli 3.0.0 → 3.0.2

data/reference.md

@@ -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>
@@ -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>
@@ -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>
@@ -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>
@@ -4734,6 +4769,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 +4940,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 +4948,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 +4956,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 +4964,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 +4972,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 +4980,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 +4988,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 +4996,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 +5012,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 +5020,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>
@@ -13254,6 +13291,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 +13420,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>
@@ -25500,7 +25541,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>
@@ -25540,6 +25581,203 @@ client.vendor.enrich_vendor(
 </dl>
 
 
+</dd>
+</dl>
+</details>
+
+<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>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+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>
+</dl>
+
+#### 🔌 Usage
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+```ruby
+client.vendor.schedule_enrichment_call(
+  entry: "8cfec329267",
+  vendor_id: 456,
+  phone: "5555550200",
+  enrichment_id: "enrich-3890-a1b2c3d4",
+  bill_id: 54323,
+  fallback_method: "check",
+  max_retries: 3,
+  timezone: "America/New_York"
+)
+```
+</dd>
+</dl>
+</dd>
+</dl>
+
+#### ⚙️ Parameters
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+**entry:** `String` — Entrypoint identifier.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**vendor_id:** `Integer` — ID of the vendor to call. Must be active and belong to the entrypoint in the path.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**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>
+
+<dl>
+<dd>
+
+**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>
+
+<dl>
+<dd>
+
+**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>
+
+<dl>
+<dd>
+
+**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>
+
+<dl>
+<dd>
+
+**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>
+
+<dl>
+<dd>
+
+**timezone:** `String` — IANA timezone identifier used to schedule the call in the vendor's local time. Defaults to `America/New_York`.
+    
+</dd>
+</dl>
+
+<dl>
+<dd>
+
+**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>
+
+<dl>
+<dd>
+
+**request_options:** `Payabli::Vendor::RequestOptions` 
+    
+</dd>
+</dl>
+</dd>
+</dl>
+
+
+</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>
+
+#### 📝 Description
+
+<dl>
+<dd>
+
+<dl>
+<dd>
+
+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>
@@ -25856,6 +26094,8 @@ 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.
+
+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.
 </dd>
 </dl>
 </dd>
@@ -26310,7 +26550,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 +26730,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 +27120,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>