#yawarshah

1 messages · Page 1 of 1 (latest)

clever ferryBOT
gilded harness
#

Could you share your use case?

drowsy bobcat
#

sure

#

So we have a subscription mechanism on our website. And when the user applies a coupon of 100%, the amount for subscription mechanism goes down to 0.

hidden garden
#

👋 stepping in for river

#

What happened when you tried that coupon? It would be helpful if you provided a sample request id req_xxx

drowsy bobcat
#

okay. Let me find it out.

drowsy bobcat
#

@hidden garden My apologies for late response, I figured out where the issue is coming from. My question to you is that due to 0.0 as payment amount, the invoice gets automatically paid even for 3Ds2, does the invoice not have a payment_intent?

#

stripe?.paymentIntents.retrieve(invoice?.payment_intent.toString())

#

in the above code, I am getting payment_intent as null and its causing problem for me.

hidden garden
#

Yes it's expected we don't create a PaymentIntent for a $0 transaction. To double check can you give me the Invoice Id?

drowsy bobcat
#

in_1LkLjxBoWPvEgUFY9686omlL

hidden garden
#

Yeah it's true that this Invoice involved a $0 transaction which didn't create the PaymentIntent. I believe it didn't event trigger a 3DS2 authentication

#

You can consider using SetupIntent, which basically will trigger 3DS2 authentication but won't charge the customer. Then after you have the SetupIntent, you can take its PaymentMethod and programmatically create the Subscription server-side, apply or don't apply the coupon as your choice

drowsy bobcat
#

ok.

#

We dont have any need to ask for the Authentication on 0.0 payment, so can we keep this flow ?? I mean it doesn't destroy stripe's recommend flow, right ?

hidden garden
#

Yes it doesn't. It's totally fine if you don't want to authenticate.

#

But keep in mind that for the next billing cycle you will need to collect a real payment method. Many merchants prefer to collect beforehand even if they are doing a discount for first cycle

#

That would help decreasing the decline rate later

drowsy bobcat
#

thank you. Let me discuss it with my team and if we are required by our PM to authenticate all the invoices.

drowsy bobcat
#

@hidden garden There is one more issue and I would love to pick your brain for the solution because we have tried everything and can't seem to understand how to tackle it.

Use Case:
End-user applies for a subscription of the product (let's say it, A) along with a payment for another product (let's say it, B) which is one time payment (instalment). Now here is the problem. We want to charge the user just once and authenticate both the subscriptions (scheduled one and normal one) but since they are different and are created separate we can't do that. Is there a way in which we can combine normal subscription with a scheduled subscription so that we can charge the sum of the total in one invoice.

hidden garden
#

Is there a way in which we can combine normal subscription with a scheduled subscription
Do you mean a subscription + an one time item?

drowsy bobcat
#

I mean subscription with a scheduled subscription (installments for the one time payment).

hidden garden
#

And you create that installments by our Subscription API, or our Subscription Schedule API?

#

It sounds like they should be 2 separated Subscription objects, and you can't combine 2 Subscription's invoices into one

drowsy bobcat
#

we create installment one with Subscription schedule api and the normal subscription with subscription api

real spruce
#

makes sense