Each API request has an associated request identifier. You can find this value in the response headers, under Request-Id
. You can also find request identifiers in the URLs of individual request logs in your Dashboard.
To expedite the resolution process, provide the request identifier when you contact us about a specific request.
Each major release, such as Acacia, includes changes that aren’t backward-compatible with previous releases. Upgrading to a new major release can require updates to existing code. Each monthly release includes only backward-compatible changes, and uses the same name as the last major release. You can safely upgrade to a new monthly release without breaking any existing code. The current version is 2025-07-30.basil. For information on all API versions, view our API changelog.
Because stripe-dotnet
is strongly typed, the requests you send align with the API version current at your stripe-dotnet
version’s release time. If you want to use a newer or older API version, consider upgrading or downgrading your stripe-dotnet
version. Use the stripe-dotnet changelog to find which versions include the API version you need.
Webhook events use the API version that’s set during your webhook’s endpoint creation. Otherwise, they use your Stripe account’s default API version (controlled in Workbench). Create a webhook endpoint with an API version equal to the version that’s pinned by your version of stripe-dotnet
, which you can determine through the StripeConfiguration.
property.
You can upgrade your API version in Workbench. As a precaution, use API versioning to test a new API version before committing to an upgrade.
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 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
Balance transactions represent funds moving through your Stripe account. Stripe creates them for every type of transaction that enters or leaves your Stripe account balance.
Related guide: Balance transaction types
The Charge
object represents a single attempt to move money into your Stripe account. PaymentIntent confirmation is the most common way to create Charges, but transferring money to a different Stripe account through Connect also creates Charges. Some legacy payment flows create Charges directly, which is not recommended for new integrations.