Additions and updates to the Stripe platform
Radar for Fraud Teams users can view payments blocked by Radar, false positive rates, and dispute trends in the new Radar report.
We've released version 16.6.1 of Stripe's Android SDK, which exposes suspend APIs to be called within a Coroutine.
You can now query the tax ids saved for your customers using the new customertaxids table.
Your customers can now use Link with Stripe to securely save their payment information and pay with 1 click on your site and across thousands of businesses using Checkout.
To speed up reconciliation, you can now include your custom metadata (such as a unique product ID or location code) when downloading financial reports.
We've added support for usage-based or tiered subscriptions—Checkout will automatically show a pricing breakdown to help customers understand the charges.
Connected accounts can now directly log in to their Express Dashboard from stripe.com, without visiting the platform’s website or app directly.
We've added support for Canadian businesses to accept Discover, Diners Club, and China UnionPay cards from customers around the world.
We’ve improved the buyer experience for Checkout by reducing the initial render time by 65%, as well as adding better loading states for slower connections.
Hosted invoice pages now have a cleaner design, automatically surface payment methods based on your customer's location, and are faster on mobile.
The PaymentMethods API now lets you set up recurring SEPA Direct Debit payments using Bancontact, iDEAL, and Sofort credentials as well.
Businesses based in Mexico can now accept OXXO using a customizable hosted voucher.
We've released version 20.0.0 of Stripe's iOS SDK, which includes Swift Package Manager support, Catalyst support, a new card scanning beta, and significantly reduces the size of our SDK by removing OpenSSL.
You can now block payments from cards linked to previous fraud activity on your account using Radar for Fraud Teams new prior_fraud_disputes_with_card attributes.
Checkout now includes a summary of your customer's purchase in their email receipt.
We now support queries using Prestosql v334 SQL syntax.
One-off invoices can now be duplicated in the Dashboard.
The Payments page now loads 2-3x faster.
You can now create Promotion codes that your customers can apply to recurring payments through Checkout.
You can now generate Promotion codes that your customers can redeem for a discount on your product or service.
You can now limit Coupons to only apply to specific products.
We've added Acquirer Reference Numbers (ARN) to the Dashboard to help your customers trace card refunds.
We’ve revamped dispute evidence submission to make it easier and faster.
We’ve reduced latency on API write calls by 7% on average (and up to 30–40% for some extreme edge cases).
We've improved the branding settings in the Dashboard to make it easier to preview and customize your email receipts, hosted invoices, and Checkout page.
You can now apply discounts when creating subscriptions by setting the coupon parameter for Checkout.
You can now customize the background color of your Checkout page.
You can now choose to automatically cancel a subscription if it's disputed.
Platforms can now update payout delay days and whether Stripe should debit a connected account for negative balances from the Dashboard.
A new field (calculatedstatementdescriptor) on charges provides a preview of the exact string we sent to card networks.
Platforms can now see the specific reason a connected account’s address has not been verified in the Dashboard.
Platforms in Australia and New Zealand can now use account debits to charge connected accounts for products or services directly from their Stripe balance.
You can now choose whether Stripe sends debit notification emails for SEPA Direct Debit payments.
You can now pause payment collection on subscriptions via the Dashboard or the API.
In addition to the succeeded webhook, we now also alert you when a payment has started processing. This applies to payment methods with delayed success confirmation.
You can now collect your customer's shipping address in Stripe Checkout.
You can now number invoices sequentially across your account instead of sequentially for each customer.
We've increased the amount of time platforms can hold funds for Express and Custom connected accounts in the US from 90 days to two years.
Express accounts now support multiple team members. Administrators can invite additional users to help manage their account.
Checkout now supports specifying tax rates when creating subscriptions.
You can now use the API to list all Checkout Sessions or filter for specific subscription or payment_intent ids.
It's now easier to compare data across time periods in the Dashboard.
Use subscription schedules to start subscriptions on a future date, backdate a subscription, automate upgrades and downgrades, and more.
You can now specify a customer when saving a payment method for future use. We’ll automatically attach the payment method to the customer once it’s set up.
You can now send invoices, receipts, and other Stripe emails from your own custom domain.
You can now query the payment method used for a charge using the new payment_method_details table.
We now provide a combined view of logs and events for payments made with the Payment Intents API in the Dashboard.
Radar can now score cards for risk even before they’re used on a transaction. Use the Setup Intents API and enable the feature in Radar’s settings.
Stripe Checkout now supports iDEAL payments in addition to cards, Apple Pay, and Google Pay.
Our new Payment Methods API now includes support for SEPA Direct Debit and iDEAL.
We’ve simplified how refunds work with the Payment Intents API: just pass the PaymentIntent id when creating a refund.
Checkout now supports subscription plans with trial periods using the subscription_data.trial_from_plan parameter.
The Android SDK is now generally available, with an improved reader pairing experience.
We've added support for the new Payment Intents API—use the payment_intents and payment_intents_metadata tables in your queries.
You can now view information about a SetupIntent in the Dashboard by searching for its object ID.
You can now use WiFi to connect a P400 card reader to your point of sale application.
Express accounts now support 5 new languages (German, Italian, Japanese, Spanish, and Simplified Chinese) for the onboarding flow, dashboard, emails, and text messages.
Set rules with the new is_off_session attribute, which detects if a customer was charged anytime after they initially completed the checkout flow.
Our updated mobile SDKs now support in-app 3D Secure 2 authentication, letting you customize the appearance of the authentication UI.
We've released version 16.0.0 of Stripe's iOS SDK and version 10.0.0 of Stripe's Android SDK. They support the Setup Intents API, allowing you to authenticate a card when it's being saved for future payments.
You can now customize the text of the payment button in Checkout by specifying a submit_type.
You can now include the Session ID in the Checkout redirect URL to easily display a confirmation when the payment is complete.
Checkout now ensures your endpoint acknowledges the checkout.session.completed webhook before redirecting your customer.
Platforms can now create Express accounts for individuals and businesses in Canada.
You can use the new INCLUDES operator in Radar rules to match substrings in metadata and string attributes. For example, ::color:: INCLUDES 'red' matches all red products ('light red', 'dark red', 'red') if you pass in custom metadata for a product's color.
You can use the new digital_wallet feature in Radar rules to detect if a payment uses Apple Pay, Google Pay, or other secure payment methods.
The hosted invoice page now accepts iDEAL, Bancontact, giropay, and SOFORT for EUR invoices.
You can now add a payment, directly from the Payment or Dispute page, to your Radar block list to prevent future payments that use the same email or credit card.
You can now add multiple tax IDs to a customer. A customer's tax IDs are displayed on invoices and credit notes issued for the customer.
You can now issue a credit note to reduce the amount of a finalized invoice.
You can now indicate a customers’ tax status on the Customer object. The customer’s tax exemption status can be one of none (the default: the customer is subject to taxes), exempt (the customer is exempt from taxes), or reverse(the EU “reverse charging” scheme applies.) This tax status will affect Invoices and Subscriptions created for that Customer.
You can now set the preferred language for a customer. This language will be used to localize invoice emails and PDFs as well as credit note PDFs.
You can now specify a name, address, and phone number for a customer. These are displayed on invoices and credit notes issued for the customer.
Tax Rates can be applied to Invoices and Subscriptions to collect and report on tax. You can apply up to five Tax Rates to Invoices, Subscriptions, InvoiceItems, and SubscriptionItems.
In addition to English, Japanese, and Italian, you can now use the Stripe Dashboard in French, Spanish, German, and Simplified Chinese.
We've updated the connected accounts page in the Dashboard with new badges, columns, filters, and sorting options so it’s easier for platforms to find and prioritize connected accounts.
We updated our API reference with instant load, search, click to copy, dark mode, and more.
Charges now have a billing_details property which displays billing information from the payment method as it was at the time of the transaction.
Charges now have a payment_method_details property which provides a consistent shape for reading the details of a payment method from the time of the transaction.
You can now customize which columns are displayed in the customer list to see what’s most important to you.
You can now export search results as a CSV from the Dashboard.
We've upgraded the Stripe Billing tables with new schemas. We now also support querying the products table.
You can now display custom fields and add a footer to your invoices.
You can now set limits on usage or amount billed on subscriptions using thresholds.
You can now access the URL for a charge or refund's receipt via the API.
You can now write rules with shipping and billing address. For example, you might write a rule to compare whether the shipping and cardholder billing address are the same.
Radar will now automatically allow any charge that is both authenticated with 3D Secure and is also protected from being disputed for fraud due to a liability shift to the issuer.
You can now set a default payment source for a subscription or an invoice.
Webhook endpoints can now be managed via the API in addition to the Dashboard.
Rules can now compare metadata on customers or destination accounts. For example, reviews could trigger if ::destination:category:: = 'new' (if you use destination objects and set a destination's 'category' metadata).
Rules can now compare numerical metadata. For example, reviews could trigger if ::customer_age:: < 21 (if you pass in custom metadata for a customer's age).
We've released version 6.0.0 of Stripe's PHP library, which includes support for automatic request retries.
3D Secure often — but not always — shifts liability for fraudulent charges from your business to the card networks. Now, you can write Radar rules based on whether there's a liability shift.
You can now set rules based on whether 3D Secure is recommended, required, optional, or not supported for a specific payment.
A source's card.three_d_secure property can now have the value recommended, indicating that the 3D Secure process can be attempted with minimal impact on conversion rate.
You can now write custom Radar rules for CVC, ZIP, and address verification using the outcomes pass, fail, unavailable, unchecked, and not_provided.
We've released version 12.0.0 of Stripe's iOS SDK, which includes support for creating tokens for Connected Accounts.
We’ve improved how we show your balances and transfers in the Dashboard.
You can now write Radar rules using the card BIN, card fingerprint, charge description, and email associated with the payment.
Our new Mastercard test number (2223 0031 2200 3222) helps you ensure your checkout flow properly handles cards starting with a 2.
The Payment Request Button Element supports Apple Pay and the Payment Request API (including Google Pay) with a single integration.
The Payment Request Button Element now exposes a click event, which enables you to detect and control when the browser payment sheet opens.
You can now update a Stripe PaymentRequest after it has been created.
You can now write custom Radar rules with CVC, ZIP code, and address verification.
Version 5.0.0 of our Android SDK lets customers manage payment sources inside your app and adds a Material-styled card input widget.
You can now @mention team members inside notes within the Dashboard.
We've simplified the flow for refunding payments in the Dashboard. Also, you can now attach notes for your teammates on refunds.
You can now specify which specific payment source to use for an invoice (e.g. ACH instead of credit card).
You can now create rules that check for missing charge attributes (e.g. email domain).
You can now receive an invoice.upcoming webhook before a subscription's renewal.
Version 4.1.1 of our Android SDK includes a utility library for Android Pay and improved support for sources.
We've released version 5.3.0 of Stripe's Java library, which includes support for expanding objects.
You can attach notes to any payment (visible to all team members) in the Dashboard.
We've released version 3.1.0 of Stripe's Android SDK, which includes support for sources.
Managed accounts are now available for marketplaces and platforms in Belgium.
You can now create Radar rules based on custom metadata on charges.
We've released version 10.0.0 of Stripe's iOS SDK, which includes support for sources.
We've added a card input widget to the Android SDK with version 3.0.1.
We’ve improved the UX for creating and editing rules.
We've released version 2.0 of Stripe's Ruby library, which includes a configurable HTTP client and support for extracting response metadata.
We’ve added a quick way to search across all our docs.
You can now send email receipts in Italian.
Checkout now supports Remember Me for Australian users.
You can now view and filter subscriptions that have been canceled in the Dashboard or via the API.
Platforms can now provide a default bank descriptor for payouts to connected accounts.
The API now includes a top-level /subscriptions endpoint.
There’s a new view in the Dashboard for managing subscriptions.
Portuguese businesses can now request an invite to our private beta.
Test payments from other countries using our new international cards.
Platforms can now create destination charges for connected accounts even with automatic transfers enabled.
We’ll be supporting Apple Pay on the Web when it launches this fall. Sign up to learn more!
Added support for accepting Discover cards with Apple Pay to our iOS library.
We added a weekly view to most graphs in the iOS Dashboard. The app also works in landscape mode now!
Businesses in Hong Kong can now request an invite to our private beta.
Singaporean companies can sign up for our public beta without an invite.
Exporting a list of disputes to a CSV is now much speedier.
Businesses in New Zealand can now request an invite to our private beta.
We’ve now linked charges to the specific transfer in which those funds will be paid out.
In addition to an account ID, the connected accounts list now also shows a meaningful name.
You can prioritize disputes by when they’re due with quick filters in the Dashboard.
With the iOS Dasboard app, you can now access your most recent payment and search faster by using Force Touch.
You can now edit metadata on customers, product, charges, and more directly from the Dashboard.
Any team member can now subscribe (or unsubscribe) to email notifications if your company receives a dispute.
We’ve added international test bank accounts for managed accounts.