[deps] Billing: Update Stripe.net to v46

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
Stripe.net	45.14.0 -> 46.2.0

---

Release Notes

stripe/stripe-dotnet (Stripe.net)

v46.2.0

• #​3002 Add ConfigureAwait calls to async calls that are awaited
  • Fixes issue #​2998 that was introduced in v46

v46.1.0

• #​2995 Update the class for ThinEvent to include Livemode and Reason
• #​2992 Remove special case Newtonsoft v12 for .net8.0
• #​2993 Update generated code
  • Remove the support for resource Margin that was accidentally made public in the last release

v46.0.0

• #​2980 Support for APIs in the new API version 2024-09-30.acacia

  This release changes the pinned API version to 2024-09-30.acacia. Please read the API Upgrade Guide and carefully review the API changes before upgrading.

⚠️ Breaking changes due to changes in the API

• Rename UsageThresholdConfig to UsageThreshold on Billing.Alert and Billing.AlertCreateOptions
• Remove support for Filter on Billing.Alert and BillingAlert.AlertCreateOptions . Use the filters on the UsageThreshold instead
• Remove support for CustomerConsentCollected on Terminal.ReaderProcessSetupIntentOptions

⚠️ Other Breaking changes in the SDK

Refer to our migration guide for v46 for a list of backwards incompatible changes in this release. Here is a summary of things to watch out for:

• Remove obsolete properties and methods from Service and ServiceNested base classes including CreateEntity and other *Entity and *EntityAsync methods, BasePath, and BaseUrl
• Rename Stripe.Event to Stripe.EventTypes. This class contains constants for event type strings.
• For more predictable naming of child services and their corresponding Options classes:
  • Rename child service classes to have the parent service's name as a prefix, e.g. CapabilityService is now AccountCapabilityService, and rename associated Options classes to match. This makes the classes more discoverable and the relationship between parent and child more clear
  • Rename Options classes for child services so that the name of the service or resource (e.g. CustomerFundingInstructions) comes before the verb (e.g. Create, List).
• Nested child service methods have been separated into separate services. These child services were previously represented as special methods within a parent service.
• Newtonsoft.Json dependency has been upgraded for all .NET target runtimes. This is potentially a breaking change if you also depend on Newtonsoft.Json directly from your application. To migrate, please upgrade the version of Newtonsoft.Json your application depends on. If you have runtime conflicts with another library dependency, you can use <bindingRedirect> to specify which version .NET should load (see https://stackoverflow.com/a/51053646 and https://learn.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/bindingredirect-element)

Additions

• Add support for UsageThreshold on Billing.AlertCreateOptions and BillingAlert
• Add support for CustomUnitAmount on ProductDefaultPriceDataOptions
• Add support for AllowRedisplay on Terminal.ReaderProcessSetupIntentOptions and TerminalReaderProcessConfigOptions
• Add support for new Usage Billing APIs Billing.MeterEvent, Billing.MeterEventAdjustments, Billing.MeterEventSession, Billing.MeterEventStream and the new Events API Core.Events under the v2 namespace
• Add method ParseThinEvent() on the StripeClient class to parse thin events.
• Add methods RawRequestAsync() on the StripeClient class that takes a HTTP method type, url and relevant parameters to make requests to the Stripe API that are not yet supported in the SDK.
• Add access to services to StripeClient under V1 and V2 property accessors, so that instead of

  StripeConfiguration.ApiKey = apiKey;
  var svc = new CustomerService();
  svc.Get(customerId);

you can write:

var client = new StripeClient(apiKey);
client.V1.Customers.Get(customerId)

This supports a move towards a services-based client pattern where a StripeClient instance consolidates configuration and service access. This enables you simultaneously use multiple clients with different configuration options (such as API keys), and makes it much easier to discover what services are available by inspecting the V1 and V2 properties (either manually or via your code editors auto-completion).

---

Configuration

📅 Schedule: Branch creation - "every 2nd week starting on the 2 week of the year before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[bitwarden-bot]

Internal tracking:

• ID: PM-13569
• Link: https://bitwarden.atlassian.net/browse/PM-13569

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[github-actions]

Checkmarx One – Scan Summary & Details – ae5d75d3-2241-4dc4-9d5a-7dac02429537

Fixed Issues

Severity	Issue	Source File / Package
	Unpinned Actions Full Length Commit SHA	/_move_finalization_db_scripts.yml: 27
	Unpinned Actions Full Length Commit SHA	/build.yml: 631
	Unpinned Actions Full Length Commit SHA	/release.yml: 63
	Unpinned Actions Full Length Commit SHA	/build.yml: 582
	Unpinned Actions Full Length Commit SHA	/version-bump.yml: 61
	Unpinned Actions Full Length Commit SHA	/_move_finalization_db_scripts.yml: 103
	Unpinned Actions Full Length Commit SHA	/cleanup-rc-branch.yml: 21
	Unpinned Actions Full Length Commit SHA	/version-bump.yml: 122
	Unpinned Actions Full Length Commit SHA	/version-bump.yml: 29
	Unpinned Actions Full Length Commit SHA	/build.yml: 548
	Unpinned Actions Full Length Commit SHA	/build.yml: 207
	Unpinned Actions Full Length Commit SHA	/version-bump.yml: 137
	Unpinned Actions Full Length Commit SHA	/version-bump.yml: 220
	Unpinned Actions Full Length Commit SHA	/build.yml: 515
	Unpinned Actions Full Length Commit SHA	/version-bump.yml: 129
	Unpinned Actions Full Length Commit SHA	/release.yml: 44

[amorask-bitwarden]

@cyprain-okeke This doesn't build as there's breaking changes in the Stripe upgrade.