#NEWJOSSY
1 messages · Page 1 of 1 (latest)
Hi there!
Hello kind sir
I'm not sure I understand your question. Can you try to rephrase, maybe by giving a concrete example of the issue?
Okay, one moment
- There is default checkout on upgrading subscription plan. User enters his card details and submits form. Payment is completed and card is attached to the customer.
- There is functionality that attaches card to the customer, setup_future_usage = "on_session", card is saved only if payment was successfull
Both cases attach cards to user. The first one is not intended to attach card to user
What is "default checkout"?
What is this screenshot? Is this the Card Element? https://stripe.com/docs/payments/accept-card-payments?platform=web&ui=elements
So this forms attach the payment method to the customer and you want to stop this?
Got it. And your issue is that customer using this form automatically get their payment method attached?
Are you using a PaymentIntent or SetupIntent for this form?
Or is it for a Subscription?
Subscription, and I see on the server subscriptionService.CreateAsync(subscriptionOptions);
Can you share one subscription ID (sub_xxx) created this way?
So I can see how/when you attach the payment method?
Sorry for the delay, having a look now!
Here's the request to create that subscription: https://dashboard.stripe.com/test/logs/req_AWs6ZFMMEZ9RVT
This request doesn't set any payment method on the subscription or the customer. So I guess there is anoter part of your code that is doing this.
👋 taking over for my colleague. Let me know if there's any follow-up Qs I can answer!