#SCIF

1 messages · Page 1 of 1 (latest)

languid fulcrumBOT
glacial urchin
#

I used 4000000000003220 CC and got weird behavior:

  1. 3ds was asked on SetupIntent, which was expected
  2. Subscription was created but not paid and new PI was created
  3. Customer had to pass 3ds again

Why did that happen? I assume that SI must solve this and the single reason of possible fail — lack of money on customer's CC

flat lichen
#

👋 Is there a time/gap between the creation + confirmation of the SetupIntent and the creation of the Subscription? Like, if you're immediately charging a customer for the subscription's first invoice, you shouldn't create a separate SetupIntent

#

also, just because a customer completed 3DS during a SetupIntent doesn't mean they won't be required to complete 3DS in the future. that's ultimately up to the issuing banks.

glacial urchin
#

I'm working on Stripe integration using Connect.
The reason why I use routine of SI + subscription creation, rather just a subscription is: Stripe account has other integrations and some customers have their default PM's but I don't want them to be charged

flat lichen
#

Stripe account has other integrations and some customers have their default PM's but I don't want them to be charged
Not sure I follow this

glacial urchin
#

How off_session should change the behavior? I could try right now

flat lichen
#

Using off_session basically flags this as a subscription that is being created while a customer is not actively within your app

glacial urchin
glacial urchin
#

I passed off_session: true and flow didn't change. Was asked second time

flat lichen
glacial urchin
flat lichen
#

Okay, let's slow down. You mentioned this: "some customers have their default PM's but I don't want them to be charged". If you're using SI to collect payment details but plan to create a subscription using the saved PM right after, you should not use SI

languid fulcrumBOT
flat lichen
tiny marsh
#

👋 taking over here

#

That meant you can simply just create a Subscription and confirm its first PaymentIntent to activate it, without the use of SI

glacial urchin
tiny marsh
#

Sorry I think let's step back and review your business scenario again. Could you explain what you want to achieve here?

glacial urchin
#

Does it make sense?

tiny marsh
#

Let's put it by steps. I see you have Connected Accounts, each of them already has customers with some saved payment method

#

Now you will want to have new Subscriptions for those customers?

glacial urchin
#

Some of customers accounts could have default PM's created by other integrations (and they have). I want to create a subscription and store PM on subscriptions to avoid affecting existing features/integrations.

#

Now you will want to have new Subscriptions for those customers?

Yep, that's the idea. To provide customers with ability to input CC (that could be the same or not the same as their default PM) and try to buy the subscription using only this newly input CC

tiny marsh
#

Yeah so it's normal to just create a Subscription and use its latest_invoice.payment_intent.client_secret to collect a new payment method. Any specific issue with it?

glacial urchin
tiny marsh
#

Hmm even if you use default_incomplete?

glacial urchin
glacial urchin
#

🤷‍♂️ May be i just need a few days off :/ Looks like it works exactly as I needed