#torstenzwoch-subscription

1 messages · Page 1 of 1 (latest)

quick oak
#

Hi there 👋 are you planning to use the Subscription objects within Stripe, or are you managing your own subscription lifecycles and just sending the payments through Stripe?

#

I ask because if you're using Subscriptions within Stripe then you don't need to create Payment Intents. When a Subscription is created it will generate it's first invoice and create an underlying Payment Intent for that invoice.

short dove
#

Mmh. I think it is the second part, but i don't know. I use stripe.js in frontend to create a custom form and send the information to my api wich creates the user, attach the payment and creat's the paymentIntent with the strip library. The client_secret was send to the frontend and here the frontend makes a confirmSepaDebitPayment

#

ok. in the tenant this was a subscription. but currently we have the problem that the first payment was execute and after 30days the payment breaks up because of a missing mandate.

quick oak
#

Gotcha, I just want to rephrase that to make sure I'm looking at the right thing. So you charged a customer via a Sepa Direct Debit, but when you attempted to charge them a second time that payment is failing?

short dove
#

At the first time (30 days free trial) the user must not pay. But if stripe want to collect the money for the next month after the 30 days, the message/status in stripe at the payment process is "requires_confirmation"

#

yesterday a stripe supporter means that the mandate to collect is missing.

quick oak
#

Hm, usually the requires_confirmation state just means the intent needs to be confirmed, do you have the ID of a Payment Intent (pi_XXX) where you saw this behavior that I can take a closer look at?

short dove
#

pi_3KLSDgJrVqBdEBVU1ievZzvn

#

i am implement stripe in our solution 7 month ago. I think i have forgot something in the payment process. I hoped that if i do the following, stripe would handle it for me.

  • Frontend use stripe.js and after user hat input his name and the iban, there was createPaymentMethod in Frontend and send the paymentMethodId with some other Date to my API
  • The API creates a Stripe user if not exits and add the paymentMethod (paymentId as default payment method to the user. Then the subscription was created and the frontend get a feedback.
  • Now the Frontend confirmSepaDebitPayment
quick oak
#

Gotcha, thank you for the additional details. I was able to see by looking at that PI that you are manually create the payment method for your customers, as you explained. This deviates a bit from our flow and as such the payment method is not fully setup for payments where the user isn't on-session.

This guide walks through the flow for saving a Sepa DD to be used on future payments:
https://stripe.com/docs/payments/sepa-debit/set-up-payment?platform=web