#[LBG] India-Checkout
1 messages ยท Page 1 of 1 (latest)
๐ happy to help
is that what you are looking for https://stripe.com/docs/checkout/quickstart ?
I do'nt want to use Checkout
there's a custom payment flow in that page I sent you
Oh sorry let met check again
The workflow I need to achieve is this : 1- display a credit card input to make the customer enter his credit card. 2- make an initial payment_intent of 1โฌ on the credit card in setup future usage mode after 3DS authentication. 3- Save the credit card. 4- If the payment_intent did go through, create a new subscription on the customer with the default payment method = the credit card authenticated previously
Do you confirm that it is possible ?
yes it is possible
but just to clarify one thing, are you doing step 2 only to setup as future usage?
No, it is just for "card authorization" from the issuer
you could always do something like capture later https://stripe.com/docs/payments/capture-later
if you just want to do a card authorization
I've though about it but it's not what we need
The 1โฌ payment immediately refunded suits more because behind this we create a subscription with a trial
what you described above is achievable I was just trying to understand whether you were jumping through extra hoops when there might be another way around
but that would cost you the Stripe fees twice
on the 1EUR payment and the subscription
Does not matter it's mandatory
1โฌ refunded immediately and then the beginning of the subscription with a trial period
Then 29โฌ/month excluding tax
It's not my business case, it's reality. I've been struggling for months with what I call "default issuer decline code" that is "insufficient funds". I've been harassing you guys for weeks and the web support to understand why we had so much "insufficient funds", no one was capable of looking beyond the tip of one's nose, all you did was telling me "there is no funds on the account", totally useless, I know how to read. I first thought it was SCA but then many little things led me to the "authorization issue". For subscriptions with trial, you have to make a first payment on_session to confirm the funds and above all get yourself known by the issuer for future off_session payments. Damn even Google does it (screenshot is for Youtube Premium with 1month trial) !!!! But it's no where is Stripe docs, tips, or even here on discord after explaining our problems 1681681681 times. We started to implement it last week, on our first small smaple we want from 10% of accepted off_session initial payment to 66% ..........
So no, it's not just our business case
It's not my business case, it's reality
Sorry I didn't mean to offend or anything, what I meant if that's a business requirement of yours then technically there's a way of doing it
Don't take it personally but I'm reaaaaaaaaally pissed-off at Stripe as we lost a lot of money and no one has tips
Anyway
I feel your frustration and I'm trying to help you on the technical integration
of what feels right for your business
So I need to use Element with stripe.js on front to create an initial payment_intent of 1โฌ
Confirm it correctly. I'll figure out a backend webhook to refunded immediately
Create the payment intent to save the credit card, set it for future usage, confirm everything correctly (3DS)
And if payment is OK, create subscription with the payment method attached to it
yes
I think @valid cape has a similar use case, I sent some steps that might be also helpful for you
I hope this might help
๐
Hi again
how can I help?
We managed to implement this workflow : 1- Create a payment_intent of 1โฌ. 2- Create an Element to gather credit card information and process payment. 3- Detect the event payment_intent.succeeded, if OK, refund the payment_intent of 1โฌ immediately, create a new subscription using the new payment_method attached
Here is a test customer on test env :cus_LczQ5ZtbRJRkm1
I have several questions
happy to help
Why is there a setup_intent still incomplete on the payment method ?
seti_1KvjY3LJLkeHRLt1x4lUOxli
how did you attach the payment_method?
Yes
evt_1KvjXxLJLkeHRLt1CUuIVAW1
Do we have to Confirm the paymentIntent AND the payment_method.attached ? That would generate 2x 3DS
could you share the code that you used to attach the payment method to the customer?
Mmh we are using JS Stripe plugins on our CMS to make it easier, so we do not have access to code. Attaching the payment method to the customer is an expected behavior as we need it for the subscription
Step 2 is the one attaching the payment method to the customer
I have no idea of what plugin you're using or how it works
What would be the expected confirmation needs in our case ?
Sorry I wouldn't be able to give you the support you're looking for, maybe you should ask the Plugin's support team
Should we confirm both the payment intent AND the setup intent when payment method attached ?
Or maybe we shouldn't have to confirm 2 times ?
What you should probably do is the equivalent of this
- create a PaymentIntent with setup_future_usage https://stripe.com/docs/api/payment_intents/create#create_payment_intent-setup_future_usage set to off_session
- make that payment method the default for the customer https://stripe.com/docs/api/customers/update#update_customer-invoice_settings-default_payment_method
- and then create the subscription
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
- create a PaymentIntent with setup_future_usage https://stripe.com/docs/api/payment_intents/create#create_payment_intent-setup_future_usage set to off_session
We do it
then no need to create another setup intent
make that payment method the default for the customer https://stripe.com/docs/api/customers/update#update_customer-invoice_settings-default_payment_method
We do it too
What is generating the setupIntent that is incomplete ?
Checking on one pont please stand by
I'll run some tests on a new version and will come back with new results ๐