Charges vs. Payment Intents APIs
Learn about the differences between Stripe’s two core payment APIs and when to use them.
Understanding the Stripe payment APIs
There are three ways to accept payments on Stripe today:
- Stripe Checkout
- Charges API
- Payment Intents API
Stripe Checkout is a prebuilt payment page that you can redirect your customer to for simple purchases and subscriptions. It provides many features, such as Apple Pay, Google Pay, internationalization, and form validation.
The Charges and Payment Intents APIs let you build custom payment flows and experiences.
We designed the Payment Intents API to be the unifying API for all Stripe products and payment methods. While we are not deprecating Charges, we plan to focus product development on Payment Intents to make it the foundational Stripe API.
For a full feature comparison, see the table below:
| Charges API | Payment Intents API |
|---|---|
| Recommended for businesses with customers primarily in the U.S. / Canada who want a simple way to accept cards. | Required for businesses that accept multiple payment methods and cards requiring authentication (e.g., due to Strong Customer AuthenticationStrong Customer Authentication (SCA) is a regulatory requirement in effect as of September 14, 2019, that impacts many European online payments. It requires customers to use two-factor authentication like 3D Secure to verify their purchase. in Europe). |
| Works on Web, iOS, and Android. | Works on Web, iOS, and Android. Can also be used to accept in-store payments with Terminal. |
| Supports cards and all payment methods on the Sources API | Supports cards, cards requiring 3DS, iDEAL, SEPA (with more to come) |
| Is not SCA ready | Is SCA readyStrong Customer Authentication (SCA) is a regulatory requirement in effect as of September 14, 2019, that impacts many European online payments. It requires customers to use two-factor authentication like 3D Secure to verify their purchase. |
Migrating code that reads from charges
If you have an application with multiple payment flows and incrementally migrating each one from the Charges API to the Payment Intents API, you should first update any code that reads from the Charge object. To help with this, the charge object has two new properties, payment_method_details and billing_details, which provide a consistent interface for reading the details of the payment method used for the charge.
These fields are available on all API versions and on charge objects created with both the Charges API and the Payment Intents API.
The following table shows commonly used properties on a charge and how the same information can be accessed using the new properties:
| Description | Before | After |
|---|---|---|
| Details about the payment method used to create a charge |
|
|
| ID of the payment method used for the charge |
|
|
| Type of payment method used |
|
|
| Billing information for the charge (e.g., billing postal code) |
|
|
| Name of the cardholder |
|
|
| Last 4 digits of the card used |
|
|
| Fingerprint of the card |
|
|
| CVC verification status for the charge |
|
|
| Card brand values |
|
|
| Google Pay enum value |
|
|
| Description | Before | After |
|---|---|---|
| Details about the payment method used to create a charge |
|
|
| ID of the payment method used for the charge |
|
|
| Type of payment method used |
|
|
| Billing information for the charge (e.g., billing postal code) |
|
|
| Name of the cardholder |
|
|
| Last 4 digits of the card used |
|
|
| Whether or not 3D Secure was successful |
|
|
| Fingerprint of the card |
|
|
| CVC verification status for the charge |
|
|
| Card brand values |
|
|
| Google Pay enum value |
|
|
Next steps
Now you have migrated code that reads from Charges, you can continue migrating your integration.