Patch URLFinder handling

generated/stripe_billing/src/usage_record/mod.rs

@@ -1,7 +1,9 @@
 /// Usage records allow you to report customer usage and metrics to Stripe for
 /// metered billing of subscription prices.
 ///
-/// Related guide: [Metered billing](https://stripe.com/docs/billing/subscriptions/metered-billing).
+/// Related guide: [Metered billing](https://stripe.com/docs/billing/subscriptions/metered-billing)
+///
+/// For more details see <<https://stripe.com/docs/api/usage_records/object>>.
 #[derive(Clone, Debug, serde::Serialize, serde::Deserialize)]
 pub struct UsageRecord {
     /// Unique identifier for the object.

generated/stripe_checkout/src/checkout_session/mod.rs

@@ -2,7 +2,7 @@
 /// one-time purchases or subscriptions through [Checkout](https://stripe.com/docs/payments/checkout)
 /// or [Payment Links](https://stripe.com/docs/payments/payment-links).
 ///
-/// We recommend creating a new Session each time your customer attempts to pay.  Once payment is successful, the Checkout Session will contain a reference to the [Customer](https://stripe.com/docs/api/customers), and either the successful [PaymentIntent](https://stripe.com/docs/api/payment_intents) or an active [Subscription](https://stripe.com/docs/api/subscriptions).  You can create a Checkout Session on your server and redirect to its URL to begin Checkout.  Related guide: [Checkout quickstart](https://stripe.com/docs/checkout/quickstart).
+/// We recommend creating a new Session each time your customer attempts to pay.  Once payment is successful, the Checkout Session will contain a reference to the [Customer](https://stripe.com/docs/api/customers), and either the successful [PaymentIntent](https://stripe.com/docs/api/payment_intents) or an active [Subscription](https://stripe.com/docs/api/subscriptions).  You can create a Checkout Session on your server and redirect to its URL to begin Checkout.  Related guide: [Checkout quickstart](https://stripe.com/docs/checkout/quickstart)  For more details see <<https://stripe.com/docs/api/checkout/sessions/object>>.
 #[derive(Clone, Debug, serde::Serialize, serde::Deserialize)]
 pub struct CheckoutSession {
     /// When set, provides configuration for actions to take if this Checkout Session expires.

generated/stripe_connect/src/account_link/mod.rs

@@ -1,7 +1,9 @@
 /// Account Links are the means by which a Connect platform grants a connected account permission to access
 /// Stripe-hosted applications, such as Connect Onboarding.
 ///
-/// Related guide: [Connect Onboarding](https://stripe.com/docs/connect/custom/hosted-onboarding).
+/// Related guide: [Connect Onboarding](https://stripe.com/docs/connect/custom/hosted-onboarding)
+///
+/// For more details see <<https://stripe.com/docs/api/account_links/object>>.
 #[derive(Clone, Debug, serde::Serialize, serde::Deserialize)]
 pub struct AccountLink {
     /// Time at which the object was created.

generated/stripe_connect/src/account_session/mod.rs

@@ -3,7 +3,7 @@
 /// We recommend that you create an AccountSession each time you need to display an embedded component
 /// to your user.
 ///
-/// Do not save AccountSessions to your database as they expire relatively quickly, and cannot be used more than once.  Related guide: [Connect embedded components](https://stripe.com/docs/connect/get-started-connect-embedded-components).
+/// Do not save AccountSessions to your database as they expire relatively quickly, and cannot be used more than once.  Related guide: [Connect embedded components](https://stripe.com/docs/connect/get-started-connect-embedded-components)  For more details see <<https://stripe.com/docs/api/account_sessions/object>>.
 #[derive(Clone, Debug, serde::Serialize, serde::Deserialize)]
 pub struct AccountSession {
     /// The ID of the account the AccountSession was created for.

generated/stripe_connect/src/country_spec/mod.rs

@@ -2,7 +2,7 @@
 /// created.
 ///
 /// These requirements can differ depending on the account's country.
-/// The Country Specs API makes these rules available to your integration.  You can also view the information from this API call as [an online guide](/docs/connect/required-verification-information).
+/// The Country Specs API makes these rules available to your integration.  You can also view the information from this API call as [an online guide](/docs/connect/required-verification-information).  For more details see <<https://stripe.com/docs/api/country_specs/object>>.
 #[derive(Clone, Debug, serde::Serialize, serde::Deserialize)]
 pub struct CountrySpec {
     /// The default currency for this country.

generated/stripe_connect/src/login_link/mod.rs

@@ -1,4 +1,6 @@
 /// Login Links are single-use login link for an Express account to access their Stripe dashboard.
+///
+/// For more details see <<https://stripe.com/docs/api/account/login_link>>.
 #[derive(Clone, Debug, serde::Serialize, serde::Deserialize)]
 pub struct LoginLink {
     /// Time at which the object was created.

generated/stripe_core/src/balance/mod.rs

@@ -1,6 +1,6 @@
 /// This is an object representing your Stripe balance.
 ///
-/// You can retrieve it to see the balance currently on your Stripe account.  You can also retrieve the balance history, which contains a list of [transactions](https://stripe.com/docs/reporting/balance-transaction-types) that contributed to the balance (charges, payouts, and so forth).  The available and pending amounts for each currency are broken down further by payment source types.  Related guide: [Understanding Connect account balances](https://stripe.com/docs/connect/account-balances).
+/// You can retrieve it to see the balance currently on your Stripe account.  You can also retrieve the balance history, which contains a list of [transactions](https://stripe.com/docs/reporting/balance-transaction-types) that contributed to the balance (charges, payouts, and so forth).  The available and pending amounts for each currency are broken down further by payment source types.  Related guide: [Understanding Connect account balances](https://stripe.com/docs/connect/account-balances)  For more details see <<https://stripe.com/docs/api/balance/balance_object>>.
 #[derive(Clone, Debug, serde::Serialize, serde::Deserialize)]
 pub struct Balance {
     /// Available funds that you can transfer or pay out automatically by Stripe or explicitly through the [Transfers API](https://stripe.com/docs/api#transfers) or [Payouts API](https://stripe.com/docs/api#payouts).

generated/stripe_core/src/token/mod.rs

@@ -7,7 +7,7 @@
 /// This guarantees that no sensitive card data touches your server, and allows your integration to operate in a PCI-compliant way.  If you can't use client-side tokenization, you can also create tokens using the API with either your publishable or secret API key.
 /// If your integration uses this method, you're responsible for any PCI compliance that it might require, and you must keep your secret API key safe.
 /// Unlike with client-side tokenization, your customer's information isn't sent directly to Stripe, so we can't determine how it's handled or stored.  You can't store or use tokens more than once.
-/// To store card or bank account information for later use, create [Customer](https://stripe.com/docs/api#customers) objects or [Custom accounts](https://stripe.com/docs/api#external_accounts). [Radar](https://stripe.com/docs/radar), our integrated solution for automatic fraud protection, performs best with integrations that use client-side tokenization.
+/// To store card or bank account information for later use, create [Customer](https://stripe.com/docs/api#customers) objects or [Custom accounts](https://stripe.com/docs/api#external_accounts). [Radar](https://stripe.com/docs/radar), our integrated solution for automatic fraud protection, performs best with integrations that use client-side tokenization.  For more details see <<https://stripe.com/docs/api/tokens/object>>.
 #[derive(Clone, Debug, serde::Serialize, serde::Deserialize)]
 pub struct Token {
     #[serde(skip_serializing_if = "Option::is_none")]

generated/stripe_fraud/src/radar_value_list/mod.rs

@@ -1,6 +1,8 @@
 /// Value lists allow you to group values together which can then be referenced in rules.
 ///
-/// Related guide: [Default Stripe lists](https://stripe.com/docs/radar/lists#managing-list-items).
+/// Related guide: [Default Stripe lists](https://stripe.com/docs/radar/lists#managing-list-items)
+///
+/// For more details see <<https://stripe.com/docs/api/radar/value_lists/object>>.
 #[derive(Clone, Debug, serde::Serialize, serde::Deserialize)]
 pub struct RadarValueList {
     /// The name of the value list for use in rules.

generated/stripe_fraud/src/radar_value_list_item/mod.rs

@@ -1,6 +1,8 @@
 /// Value list items allow you to add specific values to a given Radar value list, which can then be used in rules.
 ///
-/// Related guide: [Managing list items](https://stripe.com/docs/radar/lists#managing-list-items).
+/// Related guide: [Managing list items](https://stripe.com/docs/radar/lists#managing-list-items)
+///
+/// For more details see <<https://stripe.com/docs/api/radar/value_list_items/object>>.
 #[derive(Clone, Debug, serde::Serialize, serde::Deserialize)]
 pub struct RadarValueListItem {
     /// Time at which the object was created.

generated/stripe_misc/src/financial_connections_account/mod.rs

@@ -1,4 +1,6 @@
 /// A Financial Connections Account represents an account that exists outside of Stripe, to which you have been granted some degree of access.
+///
+/// For more details see <<https://stripe.com/docs/api/financial_connections/accounts/object>>.
 #[derive(Clone, Debug, serde::Serialize, serde::Deserialize)]
 pub struct FinancialConnectionsAccount {
     /// The account holder that this account belongs to.

generated/stripe_misc/src/financial_connections_session/mod.rs

@@ -1,4 +1,6 @@
 /// A Financial Connections Session is the secure way to programmatically launch the client-side Stripe.js modal that lets your users link their accounts.
+///
+/// For more details see <<https://stripe.com/docs/api/financial_connections/sessions/object>>.
 #[derive(Clone, Debug, serde::Serialize, serde::Deserialize)]
 pub struct FinancialConnectionsSession {
     /// The account holder for whom accounts are collected in this session.

generated/stripe_misc/src/identity_verification_report/mod.rs

@@ -3,7 +3,7 @@
 /// parameters used.
 ///
 /// You can find the result of each verification check performed in the appropriate sub-resource: `document`, `id_number`, `selfie`.  Each VerificationReport contains a copy of any data collected by the user as well as reference IDs which can be used to access collected images through the [FileUpload](https://stripe.com/docs/api/files) API.
-/// To configure and create VerificationReports, use the [VerificationSession](https://stripe.com/docs/api/identity/verification_sessions) API.  Related guides: [Accessing verification results](https://stripe.com/docs/identity/verification-sessions#results).
+/// To configure and create VerificationReports, use the [VerificationSession](https://stripe.com/docs/api/identity/verification_sessions) API.  Related guides: [Accessing verification results](https://stripe.com/docs/identity/verification-sessions#results).  For more details see <<https://stripe.com/docs/api/identity/verification_reports/object>>.
 #[derive(Clone, Debug, serde::Serialize, serde::Deserialize)]
 pub struct IdentityVerificationReport {
     /// Time at which the object was created.

generated/stripe_misc/src/identity_verification_session/mod.rs

@@ -3,7 +3,7 @@
 ///
 /// It contains details about the type of verification, such as what [verification check](/docs/identity/verification-checks) to perform.
 /// Only create one VerificationSession for each verification in your system.  A VerificationSession transitions through [multiple statuses](/docs/identity/how-sessions-work) throughout its lifetime as it progresses through the verification flow.
-/// The VerificationSession contains the user's verified data after verification checks are complete.  Related guide: [The Verification Sessions API](https://stripe.com/docs/identity/verification-sessions).
+/// The VerificationSession contains the user's verified data after verification checks are complete.  Related guide: [The Verification Sessions API](https://stripe.com/docs/identity/verification-sessions)  For more details see <<https://stripe.com/docs/api/identity/verification_sessions/object>>.
 #[derive(Clone, Debug, serde::Serialize, serde::Deserialize)]
 pub struct IdentityVerificationSession {
     /// The short-lived client secret used by Stripe.js to [show a verification modal](https://stripe.com/docs/js/identity/modal) inside your app.

generated/stripe_misc/src/reporting_report_run/mod.rs

@@ -2,7 +2,7 @@
 /// specific run parameters.
 ///
 /// Once the object is created, Stripe begins processing the report. When the report has finished running, it will give you a reference to a file where you can retrieve your results.
-/// For an overview, see [API Access to Reports](https://stripe.com/docs/reporting/statements/api).  Note that certain report types can only be run based on your live-mode data (not test-mode data), and will error when queried without a [live-mode API key](https://stripe.com/docs/keys#test-live-modes).
+/// For an overview, see [API Access to Reports](https://stripe.com/docs/reporting/statements/api).  Note that certain report types can only be run based on your live-mode data (not test-mode data), and will error when queried without a [live-mode API key](https://stripe.com/docs/keys#test-live-modes).  For more details see <<https://stripe.com/docs/api/reporting/report_run/object>>.
 #[derive(Clone, Debug, serde::Serialize, serde::Deserialize)]
 pub struct ReportingReportRun {
     /// Time at which the object was created.

generated/stripe_misc/src/reporting_report_type/mod.rs

@@ -2,7 +2,7 @@
 /// the "Activity summary" or "Itemized payouts" reports.
 ///
 /// These objects are identified by an ID belonging to a set of enumerated values.
-/// See [API Access to Reports documentation](https://stripe.com/docs/reporting/statements/api) for those Report Type IDs, along with required and optional parameters.  Note that certain report types can only be run based on your live-mode data (not test-mode data), and will error when queried without a [live-mode API key](https://stripe.com/docs/keys#test-live-modes).
+/// See [API Access to Reports documentation](https://stripe.com/docs/reporting/statements/api) for those Report Type IDs, along with required and optional parameters.  Note that certain report types can only be run based on your live-mode data (not test-mode data), and will error when queried without a [live-mode API key](https://stripe.com/docs/keys#test-live-modes).  For more details see <<https://stripe.com/docs/api/reporting/report_type/object>>.
 #[derive(Clone, Debug, serde::Serialize, serde::Deserialize)]
 pub struct ReportingReportType {
     /// Most recent time for which this Report Type is available.

generated/stripe_misc/src/scheduled_query_run/mod.rs

@@ -2,7 +2,7 @@
 /// receive a `sigma.scheduled_query_run.created` webhook each time the query
 /// runs.
 ///
-/// The webhook contains a `ScheduledQueryRun` object, which you can use to retrieve the query results.
+/// The webhook contains a `ScheduledQueryRun` object, which you can use to retrieve the query results.  For more details see <<https://stripe.com/docs/api/sigma/scheduled_queries/object>>.
 #[derive(Clone, Debug, serde::Serialize, serde::Deserialize)]
 pub struct ScheduledQueryRun {
     /// Time at which the object was created.

generated/stripe_misc/src/tax_calculation/mod.rs

@@ -1,6 +1,8 @@
 /// A Tax Calculation allows you to calculate the tax to collect from your customer.
 ///
-/// Related guide: [Calculate tax in your custom payment flow](https://stripe.com/docs/tax/custom).
+/// Related guide: [Calculate tax in your custom payment flow](https://stripe.com/docs/tax/custom)
+///
+/// For more details see <<https://stripe.com/docs/api/tax/calculations/object>>.
 #[derive(Clone, Debug, serde::Serialize, serde::Deserialize)]
 pub struct TaxCalculation {
     /// Total after taxes.

generated/stripe_misc/src/tax_settings/mod.rs

@@ -1,6 +1,8 @@
 /// You can use Tax `Settings` to manage configurations used by Stripe Tax calculations.
 ///
-/// Related guide: [Using the Settings API](https://stripe.com/docs/tax/settings-api).
+/// Related guide: [Using the Settings API](https://stripe.com/docs/tax/settings-api)
+///
+/// For more details see <<https://stripe.com/docs/api/tax/settings/object>>.
 #[derive(Clone, Debug, serde::Serialize, serde::Deserialize)]
 pub struct TaxSettings {
     pub defaults: stripe_misc::TaxProductResourceTaxSettingsDefaults,

generated/stripe_misc/src/tax_transaction/mod.rs

@@ -1,6 +1,8 @@
 /// A Tax Transaction records the tax collected from or refunded to your customer.
 ///
-/// Related guide: [Calculate tax in your custom payment flow](https://stripe.com/docs/tax/custom#tax-transaction).
+/// Related guide: [Calculate tax in your custom payment flow](https://stripe.com/docs/tax/custom#tax-transaction)
+///
+/// For more details see <<https://stripe.com/docs/api/tax/transactions/object>>.
 #[derive(Clone, Debug, serde::Serialize, serde::Deserialize)]
 pub struct TaxTransaction {
     /// Time at which the object was created.

generated/stripe_misc/src/webhook_endpoint/mod.rs

@@ -4,7 +4,9 @@
 ///
 /// Most users configure webhooks from [the dashboard](https://dashboard.stripe.com/webhooks), which provides a user interface for registering and testing your webhook endpoints.
 ///
-/// Related guide: [Setting up webhooks](https://stripe.com/docs/webhooks/configure).
+/// Related guide: [Setting up webhooks](https://stripe.com/docs/webhooks/configure)
+///
+/// For more details see <<https://stripe.com/docs/api/webhook_endpoints/object>>.
 #[derive(Clone, Debug, serde::Serialize, serde::Deserialize)]
 pub struct WebhookEndpoint {
     /// The API version events are rendered as for this webhook endpoint.

generated/stripe_payment/src/payment_method_configuration/mod.rs

@@ -3,7 +3,7 @@
 /// You can have multiple configurations with different sets of payment methods for different scenarios.  There are two types of PaymentMethodConfigurations.
 /// Which is used depends on the [charge type](https://stripe.com/docs/connect/charges):  **Direct** configurations apply to payments created on your account, including Connect destination charges, Connect separate charges and transfers, and payments not involving Connect.  **Child** configurations apply to payments created on your connected accounts using direct charges, and charges with the on_behalf_of parameter.  Child configurations have a `parent` that sets default values and controls which settings connected accounts may override.
 /// You can specify a parent ID at payment time, and Stripe will automatically resolve the connected account’s associated child configuration.
-/// Parent configurations are [managed in the dashboard](https://dashboard.stripe.com/settings/payment_methods/connected_accounts) and are not available in this API.  Related guides: - [Payment Method Configurations API](https://stripe.com/docs/connect/payment-method-configurations) - [Multiple configurations on dynamic payment methods](https://stripe.com/docs/payments/multiple-payment-method-configs) - [Multiple configurations for your Connect accounts](https://stripe.com/docs/connect/multiple-payment-method-configurations).
+/// Parent configurations are [managed in the dashboard](https://dashboard.stripe.com/settings/payment_methods/connected_accounts) and are not available in this API.  Related guides: - [Payment Method Configurations API](https://stripe.com/docs/connect/payment-method-configurations) - [Multiple configurations on dynamic payment methods](https://stripe.com/docs/payments/multiple-payment-method-configs) - [Multiple configurations for your Connect accounts](https://stripe.com/docs/connect/multiple-payment-method-configurations)  For more details see <<https://stripe.com/docs/api/payment_method_configurations/object>>.
 #[derive(Clone, Debug, serde::Serialize, serde::Deserialize)]
 pub struct PaymentMethodConfiguration {
     #[serde(skip_serializing_if = "Option::is_none")]

generated/stripe_payment/src/payment_method_domain/mod.rs

@@ -2,6 +2,8 @@
 /// Stripe Elements use registered payment method domains to control where certain payment methods are shown.
 ///
 /// Related guides: [Payment method domains](https://stripe.com/docs/payments/payment-methods/pmd-registration).
+///
+/// For more details see <<https://stripe.com/docs/api/payment_method_domains/object>>.
 #[derive(Clone, Debug, serde::Serialize, serde::Deserialize)]
 pub struct PaymentMethodDomain {
     pub apple_pay: stripe_payment::PaymentMethodDomainResourcePaymentMethodStatus,