#_greggles_

1 messages · Page 1 of 1 (latest)

grave folioBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

wind patio
#

Do you have an example Subscription ID that I can review? The PaymentElement should automatically create a mandate so I'd like to pull up logs for a Subscription where the attached PaymentMethod had an inactive mandate

vapid bough
#

Sure, thank you.
sub_1Oa3sMGxG8m2870UcJBzOVcM

#

The payment was successful.

#

I'm creating a payment element with the subscription mode enabled so I assumed it would populate payment methods capable of recurring payments.

wind patio
#

I see you're using our deferred intents flow to first create a PaymentMethod and then create the Subscription

vapid bough
#

Yes, that's correct. Is that not prefered?

wind patio
#

Client side, did you use mode: 'subscription' for the PaymentElement?

vapid bough
#

I did

#
    const options = {
      mode: 'subscription',
      amount: 9995,
      currency: 'usd',
      paymentMethodCreation: 'manual',
      // Fully customizable with appearance API.
      appearance: appearance
    };
wind patio
#

I see a mandate was created for that US bank account PaymentMethod but that mandate's status was changed to inactive since it was of single_use type.

vapid bough
#

That's what I assume happened.

#

Is there a way to make it multi0use?

wind patio
#

Client side, could you also pass setupFutureUsage: off_session , try again, and let me know if you see something different?

vapid bough
#

sub_1Oa4f4GxG8m2870UYQMM2sie

#

Looks like an incomplete transaction

wind patio
#

Hm, did you change anything else in your client side code? I see stripe.confirmPayment hasn't been called yet

vapid bough
#

Let me run the scenario again. I only added the setupFutureUsage: off_session param you sent but I did choose a different product.

#

For clarification: the setupFutureUsage:offsession should be added to the options for creating the payment element?

wind patio
#

Yep, and that's setupFutureUsage:off_session (note the underscore)

vapid bough
#

sub_1Oa544GxG8m2870U088VwND9
The payment method still has an inactive mandate