#caleb-paymentelement

1 messages · Page 1 of 1 (latest)

fast yoke
fast yoke
#

I want to say that PaymentElement should already collect those fields for you (i.e. show them), since that is the point of PaymentElemnet

#

admittedly, I haven't tried that beta but my opinion is that it should already show those fields

bright lotus
#

That was my thought as well, but it does not

fast yoke
#

so maybe a/ you're not in the beta correctly or b/ maybe an integration issue?

#

can you share the PaymentIntent ID you used for that PaymentElement instance?

bright lotus
#

I'm using a SetupIntent flow (this is for a recurring transaction). The SetupIntent id is seti_0K2I7M53soKKKIrdRYrxNXqB_secret_KhhWOITFBAV43qZjqZ9M7d8UaHLbc6V

#

Sorry, that's the client secret

#

SetupIntent id: seti_0K2I7M53soKKKIrdRYrxNXqB

fast yoke
#

thanks, looking

bright lotus
#

I need to step away for a bit, I'll check back in on this when return.

fast yoke
#

ok so I haven't tested this (would quickly prototype but Discord is busy) but I think this is expected, I think a modal will show up after this, that allows you to enter your account details, when you call confirmSetup() or confirmPayment() , mind trying that?

what do you see with a PaymentIntent (instead of a SetupIntent)

#

yeah pretty certain that the modal that shows up is where customers enter their account details

bright lotus
#

I tried calling that, but I get back the error Missing required param: payment_method_data[us_bank_account]., which sounded like it was asking for the account information.

void onyx
#

Which beta header are you using? Is it v2?

bright lotus
#

Yes - Stripe.api_version = "2020-08-27;us_bank_account_beta=v2"

void onyx
#

I believe you should be using the v1 header if you want to use this beta with the payment element

bright lotus
#

Okay, I'll try that. Does that need to be passed in the Stripe.js request as well, or just when creating the SetupIntent server-side?

void onyx
#

I think you'd only need it in the server-side request but I'm not 100% sure (never tried this beta out myself). Try it out and see what happens

bright lotus
#

Okay, changing to the v1 header in both the server side setup and the betas param for Stripe.js fixed the issue. Since the v2 is not working with the PaymentElement, do you know if we can plan on the finished product supporting the PaymentElement for our Connect integration?

void onyx
#

Unfortunately I'm not the best person to ask for that since I don't know the specific timelines for getting v2 ready. I'd recommend reaching out to whoever helped get you into the beta and checking with them

bright lotus
#

Thanks, I'll check with our account manager.