Stripe Billing Integration Series: Part 1 of 3
You are reading: Overview (applies to all clients)
See the Client Guide Series index for Part 2 (Setup) and Part 3 (Manage Subscriptions), each available in a Stripe Payments and a BYOP version.
Overview
Piano's Stripe Billing integration combines Piano's flexible subscription management with Stripe's advanced billing infrastructure and AI-powered revenue recovery capabilities. This integration maintains Piano as your primary interface for subscription operations while leveraging Stripe's billing engine to handle payment processing, invoicing, and automated retry logic.
The Piano integration with Stripe is being released in phases.
Non-Stripe payment providers (Bring Your Own Processor, or BYOP) are now supported. See the BYOP version of Part 3 in the series index for full details. This documentation will be updated as further enhancements are released.
This article provides a general overview of the Stripe Billing integration. For a complete breakdown of all configuration steps, supported features, and detailed implementation instructions, see the Stripe Billing Integration technical reference.
What Piano does and what Stripe does
Piano Subscriptions (Management + Billing) owns your terms and offers, pricing and proration, promotions and vouchers, tax calculation, access control and grace periods, Checkout and My Account, subscriber emails through Email Manager, the Publisher Dashboard and API, upgrade and downgrade logic, Subscription Insights reporting, and the connection to your payment processor when you use BYOP.
Stripe Billing owns the subscription schedule, invoice generation and finalization, the renewal clock, and payment retries through Smart Retries when the payment method is Stripe-native.
Stripe Payments, if you use it, owns the card charge, PCI scope for card data, and Stripe's financial reporting.
What changes for you: Piano is still where you manage subscriptions. Renewals are now driven by Stripe's billing clock rather than Piano's. If you use Stripe Payments, retry configuration moves out of Passive Churn Prevention in Piano and into Revenue Recovery in Stripe, and Passive Churn Prevention settings no longer affect those subscriptions.
What does not change: everything you configure in Piano stays in Piano. Terms, offers, promotions, emails, and access rules are unaffected.
What's New with Stripe Billing
Enhanced Revenue Recovery
Your subscriptions now benefit from Stripe's AI-driven Smart Retries, which recover failed payments by:
-
Learning from Stripe's network of billions of transactions
-
Timing retry attempts when payments are most likely to succeed
-
Automatically optimizing retry strategies based on real-time signals
Stripe reports that businesses using Stripe recover on average 55% of failed payments, and that 92% of cards have been seen before on the Stripe network. These are Stripe's own published figures and are subject to change.
Improved Billing Date Management
Monthly and annual subscriptions now maintain their original billing dates even when adjusted for shorter months:
-
Example: A subscription starting January 31st will bill on February 28th (or 29th), then return to March 31st
-
Previously, the February 28th date would become the permanent billing date
Better Direct Debit Handling
Subscriptions using SEPA, BACS, or ACH payment methods now receive Smart Retry treatment, maintaining subscriber access during the retry period rather than immediately canceling.
Non-Stripe Processors Now Supported
Non-Stripe payment processors, including Braintree, Datatrans, and other PSPs, are now supported via the Bring Your Own Processor (BYOP) feature. Publishers can switch existing and new subscriptions to Stripe Billing while retaining their current payment processor. Stripe manages the subscription and invoice lifecycle; Piano handles payment collection through your PSP. See the BYOP version of Part 3 for full details.
Subscription Upgrades available
Subscription upgrades (moving a subscriber from one payment term to another) are now fully supported for all Stripe Billing managed subscriptions. All upgrade channels (My Account, Checkout, Publisher Dashboard, API, and Action Manager) use Stripe's subscription-first model: the plan change is applied immediately, and payment is collected after. Payment failure results in a grace period with Smart Retries, not a rollback. Publishers using MA/PD/API sync upgrade flows should review the Subscription Upgrades section in Part 3 for more details.
Key Differences with Stripe Billing
Grace Period Behavior
Important Change: When using Stripe Billing with Smart Retries:
-
Grace period length now equals your billing period (e.g., 1 month for monthly subscriptions)
-
Retry timing is AI-driven rather than following a preset schedule
-
A single renewal failure notification is sent instead of multiple notifications per retry
-
Previous Passive Churn Prevention configurations no longer apply to Stripe-managed subscriptions
The exception is 3DS re-authentication. Smart Retries do not start automatically for a 3DS re-authentication failure, and Piano applies a fixed 30-day grace period instead of a grace period equal to your billing period.
For BYOP subscriptions: the access extension trigger is invoice.finalized (not invoice.paid). Access is extended when Stripe finalizes the renewal invoice, before payment is confirmed. Dunning and retry logic uses Piano's retry schedule (not Stripe Smart Retries) for BYOP methods. For BYOP async methods (direct debit, bank transfer), upgrade payment failures result in immediate cancellation without a grace period.
Passive Churn Prevention vs Revenue Recovery (Smart Retries) Differences
|
Passive Churn Prevention |
Smart Retries and Automations |
|
Supports charge retries with various cadences or on custom days of the grace period. |
Supports AI-driven charge retry schedule not visible to clients, only next retry attempt is available. Retries are not evenly distributed across the period. |
|
Supports up to 10 retry attempts within a grace period of up to 60 days. |
Retries run on an AI-driven schedule. You choose the retry window (1 week, 2 weeks, 3 weeks, 1 month, or 2 months) and the number of attempts. Stripe's recommended setting is 8 attempts within 2 weeks. A fixed custom retry schedule is also available, limited to 3 attempts. |
|
Supports different customizable logics based on the initial charge failure code. |
Supports AI-driven charge retry logics. |
|
Supports sending customized email notifications for each charge retry attempt. |
Supports a single version of failed renewal email notification for all charge retry attempts. |
|
Supports different grace period length per logic. |
Supports single retry period length per application. Unless Automations are used which allow separate logic for monthly vs annual. |
|
Supports term-based configurations. |
Supports single configuration for the whole application that will be applied to all types of subscriptions (weekly, monthly, annual) or multiple automations configurations. |
|
Supports retries on manually defined cadence. |
Supports AI-driven charge retry times. |
|
Supports multiple payment providers with synchronous payment methods only. |
Supports card-based methods, with separate logic for ACH and SEPA payment methods. |
Renewal Processing
Synchronous Payments (e.g. Cards):
-
Renewal date arrives
-
Payment attempt made immediately
-
If successful: subscription renewed, access continued
-
If failed: Smart Retry begins, access extended during retry period
Asynchronous Payments (e.g. Direct Debit):
-
Invoice created and finalized
-
Subscription renewed, access granted
-
Payment collection initiated
-
If payment fails: Smart Retry begins while maintaining access
Please note that any single billing period (a billing plan, trial, or access period) can run for up to 3 years. For more details, see Billing periods and the 3-year guideline.
Supported Features
New Purchases
-
Single and recurring payment terms
-
Dynamic terms
-
Free and paid trial periods
-
Promotions and discounts
-
Shared access subscriptions
-
Stripe Credit Cards, Elements, and Apple Pay
-
Non-Stripe payment providers
-
Gift purchases (creates Stripe Invoice with purchase-date service period)
Subscription management
-
Auto-renewal toggle
-
Next billing date changes
-
Immediate cancellation
-
Payment method updates
-
Billing address updates
-
Full and partial refunds
-
Immediate subscription upgrades (payment terms, same currency)
-
Deferred (end-of-billing-cycle) subscription upgrades
-
Pending upgrade cancellation, suspension, and resumption
-
Manual renewal in MyAccount and Dashboard
Payment Methods and Countries
This section describes the payment methods and markets supported by the Piano Stripe Billing integration. The integration includes Stripe-native methods, BYOP (Bring Your Own Processor) integrations for clients using existing payment processors, and Piano-managed market support for select regions where Stripe does not offer direct merchant accounts.
Stripe-native payment methods
The following payment methods are supported through the Stripe-native integration. Cards, Apple Pay, Google Pay, and Link are enabled by default in Stripe. The others are off by default, so you must enable them in your Stripe payment method settings before you can use them.
|
Payment method |
Type |
End-customer region |
Enabled in Stripe by default |
|---|---|---|---|
|
Cards (Visa, Mastercard, Amex, Diners, JCB, UnionPay, Cartes Bancaires) |
Card |
Global |
Yes. JCB, Korean cards, and Japan installment cards are off by default and must be enabled in your Stripe payment method settings. |
|
Apple Pay |
Wallet |
Global, except India, where Stripe does not support Apple Pay |
Yes |
|
Google Pay |
Wallet |
Global, except India, where Stripe does not support Google Pay |
Yes |
|
Link |
Wallet |
Global |
Yes |
|
SEPA Direct Debit |
Bank debit |
European Union |
No. Enable it in your Stripe payment method settings. |
|
Bacs Direct Debit |
Bank debit |
United Kingdom |
No. Enable it in your Stripe payment method settings. |
|
iDEAL |
Bank redirect |
Netherlands (converts to SEPA mandate for subscriptions) |
No. Enable it in your Stripe payment method settings. |
|
ACH Direct Debit |
Bank debit |
United States |
No. Enable it in your Stripe payment method settings. |
Additional Stripe Elements methods (TWINT natively, OXXO, Boleto, BLIK, Klarna, PayPal via Stripe, and others) are available in Stripe but are not yet enabled in Piano. These are subject to the Piano Management + Billing roadmap and will be listed under Features Coming Soon as they are enabled.
Bring Your Own Processor (BYOP) integrations
With BYOP, Piano connects to your existing payment processor for charge collection while Stripe Billing manages the subscription schedule and invoicing. The following processors and connectors are supported:
|
Processor / Connector |
Supported payment methods |
Region |
|---|---|---|
|
Braintree |
Credit Cards, Apple Pay, Google Pay, PayPal |
Global |
|
PayPal (Express Checkout / PPCP) |
PayPal, Cards, Venmo |
Global |
|
Cybersource |
Credit Cards (including TWD for Taiwan) |
Global, Taiwan |
|
Datatrans |
Credit Cards, Apple Pay, Google Pay, PayPal, TWINT, PostFinance |
Switzerland, EU |
|
Payway |
Credit Cards (USD, CAD), Apple Pay |
US, Canada |
|
GoCardless Drop-in |
SEPA Direct Debit, Bacs Direct Debit, ACH, BECS |
EU, UK, US, Australia |
|
GMO |
Credit Cards (JPY), Carrier Billing (Au, Docomo, SoftBank) |
Japan |
|
Sony Payments |
Credit Cards (JPY) |
Japan |
|
Vipps |
Mobile Payment |
Norway |
|
Zlick |
Carrier Billing |
Baltics |
|
Invoice Options 1 & 2 |
Invoice / Bank Transfer ( |
Global |
Piano-managed markets
Stripe does not offer direct merchant accounts in these markets. Piano manages the account infrastructure on your behalf. Contact your Piano account team to request account creation.
|
Country |
Available payment methods |
Currency |
Provider (via BYOP) |
|---|---|---|---|
|
Colombia |
Credit Cards, PSE Bank Transfer |
COP |
PayU Colombia |
|
Argentina |
Credit Cards |
ARS |
PayU Argentina |
|
Chile |
Credit Cards |
CLP |
PayU Chile |
|
Peru |
Credit Cards |
PEN |
PayU Peru |
|
Paraguay |
Credit Cards |
PYG |
Bancard |
Once your application has been switched to Stripe Billing, you can also request access to the Stripe account. Please inquire with the Piano support team if desired.
Features Coming Soon
Some features are not yet available with Stripe Billing but are planned for future releases. See the Coming Soon list on Feature Support and Roadmap for the current list.
Continue the Stripe Billing Integration Series
Next: Part 2 (Setup) and Part 3 (Manage Subscriptions), each in a Stripe Payments and a BYOP version. See the Client Guide Series index.