sive_best-practices

[crimson ember]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1219859229402337300

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[forest sedge]

Stripe will inform issuer that the recurring payments on subscription is off session, but whether 3DS is required is up to the card issuer

[void lake]

For the first part of the first month of the subscription if they are going through my payment flow I can mark it on_session or do I need to create a customer_session?

[forest sedge]

How do you integrate Subscription with Stripe currently? Direct Subscription API or Checkout Session?

[void lake]

Currently I use a checkout_session and wait for the checkout.session.complete webhook to deliver metadata for what service is to be delivered to a particular user.

I would like to make the experience flow a bit better and client just use a empty checkout session to add their card and then we can create a subscription or payment_intent for a particular service whether its once time or recurring.

This way also makes it easier to track within my database as I can deliver multiple services in a users cart more easily as i can create individual subscriptions for each item rather than multiple subscription_items on a single subscription where its harder to unsubscribe from one service at a time.

[void lake]

It might be better to demonstrate my needs with how my frontend currently exists and how I would like to make some changes.
This is it currently, it takes you right to a subscription page for just a single item so that i can have a one to one mapping of stripe subscriptions to services I deliver:

I would like my payments page to look something like this when a customer has a payment method and when there is no payment method:

[forest sedge]

In a single subscription, unsubscribing an item shouldn't be hard as it only requires deleted flag to set to true when updating a subscription: https://docs.stripe.com/api/subscriptions/update#update_subscription-items-deleted

You can use https://docs.stripe.com/payments/save-and-reuse to save a payment method first, then set it to default_payment_method of a Subscription creation later: https://docs.stripe.com/api/subscriptions/create#create_subscription-default_payment_method

In any case, whether to challenge customer 3DS, it's up to the card issuer. The more payment requests sent at the same time, the higher the likelihood 3DS will be challenged

[void lake]

Is there any easy way to test 3DSecure to be able to make a frontend and backend compatible?

[forest sedge]

What do you mean by frontend and backend compatible on 3DS? Stripe provides 3DS test card for testing in test mode: https://docs.stripe.com/testing#regulatory-cards

[void lake]

My apologies I didnt know there was a card the automatically triggered 3dsecure, that will be very helpful, much appreciated River!