Stripe VS stripe-python

Stripe iOS SDK: iOS SDK versions 22.8.1-22.8.3 contain updates to PaymentSheet, CardScan, and Identity, as well as bug fixes for Financial Connections and the Card Scan UI.

Stripe iOS SDK: iOS SDK versions 22.6.0 - 22.8.0 were released this month. These updates contain fixes and updates for PaymentSheet and Apple Pay.

Stripe iOS SDK v22.6.0: The stripe-ios v22.6.0 release includes support for Link payment method on payment sheets, adds the ability to capture selfie images in the native component flow for Identity, and fixes several bugs related to Identity.

Stripe iOS SDK v22.5.1: In iOS SDK version 22.5.1, you can now use PaymentSheet.ApplePayConfiguration.paymentSummaryItems to directly configure the payment summary items displayed in the Apple Pay sheet. This is useful for recurring payments.

Stripe iOS SDK version 21.11.0 and 21.10.0: iOS SDK version 21.11.0 introduces several payment methods in the PaymentSheet including Afterpay/Clearpay, EPS, Giropay, Klarna, P24, and more. Version 21.10.0 introduces the StripeCardScan beta.

Stripe iOS SDK version 21.9.0: iOS SDK version 21.9.0 introduces several new features to PaymentSheet, including support for more payment methods like SEPA Direct Debit, Bancontact, iDEAL, and Sofort as well as support for setting up future usage for cards, Apple Pay, and Google Pay.

Stripe iOS SDK version 21.8.0: This new iOS SDK release adds support for Stripe Identity on iOS. Read more in the docs.

Make async requests in the beta release of stripe-python: The stripe-python beta channel now has built-in support for async control flow, backed by the httpx or aiohttp http libraries.

Instantiate StripeClient in the Python SDK: Stripe-python v8.0.0 introduced StripeClient, upgrading from a single global configuration to enable multiple thread-safe instances.

Let's start by installing the Python library for Stripe, which is available on Github.

Use types with the Python SDK: Strengthen Python integrations with type annotations using the stripe-python library starting in v6.8.0b3 through the beta channel.

You should use the python package that stripe provides: https://github.com/stripe/stripe-python

The api_key is being passed down to every object. You can see it being fed to the constructor for Customer because it is a child of StripeObject.

I've been maintaining async-stripe for over a year. It is the only async client for Python. It fixes a long standing feature request (issue #327).

New API version released: Version 2022-08-01 of the Stripe API has been released along with major version upgrades to all official client libraries, namely Dotnet, Go, Java, PHP, Node, Python, and Ruby. Read more about breaking changes in the API upgrades section and how to upgrade.

> Every time a new language comes out we have to recreate millions of baseline libraries and it just sucks. As a dev I want to be able to make use of great libraries oblivious to what they are created with.

Technically this tool mostly does exist already with the OpenAPI specification if we're talking about REST APIs. If you put in the leg work to create a very detailed specification which is a YAML file, you can generate programming language specific SDKs out of it.

Stripe has publicly mentioned[0] they mostly use this spec to generate their SDKs (even as of a few years ago), even so auto-generated code still requires developer time and there's a level of "hey we're dedicated to internally supporting this". It's a huge deal having a provider internally support your language's SDK.

[0]: https://github.com/stripe/stripe-python/issues/694#issuecomm...

The stripe package is actually maintained by Stripe.