Graph/e7447fcc-7533-4092-85e0-1aaa4bb22c37

Domainunvalidated

Subscription Billing

e7447fcc-7533-4092-85e0-1aaa4bb22c37

Node Details

Public graph metadata

Updated4/30/2026

PageRank0.0002

Effectiveness0.000

Connections

38 linked nodes

RELATES_TOProblem

the first invoice is always immediately charged — Use checkout to create subscription. Tension: without waiting for the webhook to process succesfully.

PERTAIN_TOSolution

Use Stripe’s recommended payment method collection via Checkout, Elements, or the mobile SDK instead of ditching Elements; if collecting card details yourself via the API, ensure SAQ D compliance and follow Stripe’s steps to enable access to raw card data APIs.

PERTAIN_TOProblem

the frontend fails when calling stripe.confirmPayment with a specific error about setup_future_usage — using the ExpressCheckoutElement for Google Pay and Apple Pay. Tension: The same backend logic works perfectly for standard credit card payments using the CardElement. Outcome: set `mode: 'subscription'` when setting up your elements instance on your page.

PERTAIN_TOSolution

you will want to set `mode: 'subscription'` when setting up your elements instance on your page — this intent is coming from a subscription's payment intent. Tension: that should ensure that the ECE uses the proper setup future usage setting when confirming the intent. Outcome: That should ensure that the ECE uses the proper setup future usage setting when confirming the intent.

PERTAIN_TOProblem

the invoice does not finalize after simulating a clock advancement of 1 hour (even weeks) — I use test clocks to simulate the subscription. Tension: I would have expected that the invoice was already finalized. Outcome: the invoice was actually finalized by advancing with test clock by an additional hour.

PERTAIN_TOProblem

Strapi’s Stripe webhook endpoint logs incoming events, but every request fails with “No stripe-signature header value was provided.” This prevents Stripe webhook signature verification from succeeding during local testing.

PERTAIN_TOSolution

Test Clocks? They are a way to simulate the advancement of time for Stripe subscriptions. — You can use Test Clocks to simulate monthly & annual subscription cycles in seconds. Tension: you do need to wait while the clock advances before you call the API again. Outcome: it will trigger the webhook events.

PERTAIN_TOProblem

I want to know if I can use the stripe express checkout element for subscription? — I use ruby btw. Tension: one of the modes made it seem possible. Outcome: You can use their Express Checkout Element for subscriptions.

PERTAIN_TOSolution

You can use their Express Checkout Element for subscriptions. — on the client site you would specify the mode to subscription. Outcome: use their `stripe.subscriptions.create` method.

PERTAIN_TOSolution

Attach paymentMethod.id to customer. — I use Ruby for the backend. Outcome: Set payment method as default:.

PERTAIN_TORootCause

Whether or not you want to use Stripe Checkout. — Checkout allows you to "mix" the items in a single Checkout Session to include both one-off and subscription prices - mixed cart. Tension: if you don't want to use Checkout Sessions, then you will need to create Subscriptions with the `add_invoice_items` parameter. Outcome: Checkout allows you to "mix" the items in a single Checkout Session.

PERTAIN_TOProblem

How to process it as one single purchase? — A buyer wants to purchase a monthly pass (which is subscription $10/month) and some other item (which is one-time item $5). Tension: It supposes to charge them $15 this time and $10 every following month. Outcome: There are a couple ways you can accomplish this.

PERTAIN_TOSolution

Checkout allows you to "mix" the items in a single Checkout Session — Non-Checkout. Tension: then you will need to create Subscriptions with the `add_invoice_items` parameter. Outcome: bundle recurring prices and one-off prices on the same Invoice.

PERTAIN_TOProblem

Trying to implement Stripe subscriptions from a Dart Frog server-side endpoint, but the approach using the REST API/library is unclear and the subscription creation flow is failing or not working as expected.

PERTAIN_TOProblem

invoice.payment_failed fires on failed recurring invoice payments, but subscription cancellation timing is unclear

PERTAIN_TOSolution

For every failed payment attempt on the recurring invoice payments, an `invoice.payment_failed` event will be sent. — If my user join to the monthly product, he pays the first month by credit card, then he uses his subscription normally during the time he is entitled to. Tension: Only when the payment retries are exhausted, the subscription will be canceled, marked as `unpaid` or left it as `past_due` depending on your "Manage payments that require confirmation" setting in Dashboard. Outcome: Your system should listen to `invoice.payment_failed` event and follow the guide here to recover the payment failures: https://docs.stripe.com/billing/subscriptions/webhooks#payment-failures.

PERTAIN_TOProblem

there's no way to get an upcoming or preview Invoice for the Subscription — If you have `trial_settings.end_behavior.missing_payment_method` set to `pause` and there's no Payment Method available. Tension: The subscription will pause at the end of the trial instead of generating an invoice because the customer has not provided a payment method. Outcome: that's the only way.

PERTAIN_TOSolution

Update the Subscription to change `trial_settings.end_behavior.missing_payment_method` to `create_invoice` — Retrieve an upcoming or preview Invoice. Tension: The Stripe API doesn't support changing `trial_settings.end_behavior.missing_payment_method` when retrieving an upcoming or preview Invoice. Outcome: Update the Subscription again to revert `trial_settings.end_behavior.missing_payment_method` to `pause`.

PERTAIN_TOProblem

the first invoice is always immediately charged — Use checkout to create subscription. Tension: without waiting for the webhook to process succesfully.

PERTAIN_TOSolution

create the subscription with `trial_end` set a couple of seconds into the future — Checkout Sessions require `trial_end` to be 48 hours in the future. Tension: you can't use Checkout Sessions for this. Outcome: The subscription will first generate a $0 invoice, and once the trial is over a non-zero invoice will be created with a one hour draft period.

PERTAIN_TOSolution

use the Payment Element to collect payment instead — collect the PaymentMethod first then create a subscription schedule. Tension: You will need to collect the PaymentMethod first then create a subscription schedule. Outcome: these guides may be useful.

PERTAIN_TOSolution

Make a GET call to /v1/invoices/upcoming with subscription_details[items][0][price], customer, automatic_tax[enabled]=true, and optional discounts[0][coupon]

PERTAIN_TOProblem

Using Stripe Checkout to let a customer add a second service later (not at the same time) with a discounted bundle price, ideally as the same subscription with a higher total amount.

PERTAIN_TOSolution

Use Stripe Checkout only to start the subscription, then when the customer adds the second service later, update the existing subscription by adding the new item/price via the Subscriptions Update API. Apply the bundle discount through your pricing/discount logic when updating the subscription.

PERTAIN_TOProblem

updating the Subscription with a pending update while it's attached to a Subscription Schedule - which works — while it's attached to a Subscription Schedule. Tension: the update at Subscription-level isn't reflected on the Subscription Schedule. Outcome: you might need to modify the phases slightly depending on your use-case.

PERTAIN_TOSolution

updating the Subscription with a pending update while it's attached to a Subscription Schedule — while it's attached to a Subscription Schedule. Tension: the update at Subscription-level isn't reflected on the Subscription Schedule. Outcome: that still looks better than the other options.

PERTAIN_TOSolution

get the `latest_invoice` ID and then make a call to finalize the invoice using the API — since you're explicitly using `prorate_behavior=always_invoice`. Tension: Stripe waits about an hour before finalizing the invoice and attempting payment. Outcome: testing this with your test API key to ensure this is the behavior you want to see is a good next step.

PERTAIN_TOSolution

Use the Stripe API (e.g., subscriptions/create) to create customers and subscriptions, and use a Flutter Stripe package to collect/create a payment method that will be attached/used for the subscription.

PERTAIN_TOProblem

I have successfully created checkout sessions and webhooks. Now I have stored $SubscriptionID and want to check the status of my subscription with Stripe. Tension: the call `$stripe = new \Stripe\StripeClient($secretKey);` creates a Stripe client. This lets you access all the API methods. It doesn't store any information about the responses to various API requests. Outcome: What you need to store is store the returned value of each call.

PERTAIN_TOSolution

What you need to store is store the returned value of each call. — $subscription = $stripe->subscriptions->retrieve($SubscriptionID, []);. Tension: So you can do `$subscription->id` or `$subscription->status` after that. Outcome: This will give you a $subscription variable that has all the properties of a Subscription object.

PERTAIN_TOSolution

Stripe has released the customer-session-client-secret attribute for the Pricing Table — for the Pricing Table. Tension: that allows a pricing table to be used with an existing customer. Outcome: allows a pricing table to be used with an existing customer.

PERTAIN_TOProblem

I see no way to initiate this event directly from the dashboard. — when using a hosted endpoint with ngrok or any other tunneling tool. Tension: I have to wait until the end of the month for the event to trigger. Outcome: my manager won't appreciate me waiting for that long.

PERTAIN_TOProblem

if the same customer subscribe to differ — When we render pricing table - we use "customer-email" property so on the checkout page email input is prepolulated and disabled. Tension: subscriber company can have multiple subscriptions. Outcome: we decided to move forward with pricing tables.

PERTAIN_TOProblem

I am confused about the client Secret key. — I am using ionic 5 angular 14 capacitor 5 WITH PHP AS BACKEND. Outcome: The client_secret is obtained from a PaymentIntent.

PERTAIN_TOSolution

you can manually finalize it as soon as it's been created — when it's a draft. Tension: there won't be any modifications needed to the Invoice. Outcome: yes, you can manually finalize it as soon as it's been created.

PERTAIN_TOSolution

If you want to use the Payment Element, you can create either a PaymentIntent or SetupIntent. Tension: Checkout Sessions and the Payment Element are two separate/different integration paths. Outcome: use the corresponding `client_secret` [0][1] which looks like `pi_..._secret_...` and `seti_..._secret_...` respectively.

PERTAIN_TOProblem

my unpaid subscriptions marked with "Past due", due to the 3DS — in the test environment. Tension: I find invoice.payment_action_required and "...payment for an invoice for € xxx requires a verification step by the user". Outcome: If you omit `request_three_d_secure`, the Subscription renewal should proceed without requesting for 3DS.

PERTAIN_TOSolution

If you omit `request_three_d_secure` — When you include that parameter. Outcome: the Subscription renewal should proceed without requesting for 3DS.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info