#groarq_api

1 messages · Page 1 of 1 (latest)

devout pebbleBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1271011371437264947

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

inner gazelle
knotty sinew
#

I just figured out what is the problem, but still have no idea why it happens. I wanted to give you req IDs I have but on single page we are loading two stripe JS elements. One for card and second is for US bank account - we want to have them separately.

So that we have one setup intent with "payment methods: 'card'" - req_CrmWBt8F8ifMMs
and second with "us_bank_account" - req_hkm8gwOsclxOSC

Then, both are generating elements session:
req_8mtpipm6j9pmg9
req_vkd0Pp2Li2uJ5F

When I removed bank JS element, the one for card worked. But it does not work when the second element is loaded.

brisk seal
#

hi! I'm taking over this thread.

knotty sinew
#

Hello

#

If only I would know what this "current account" is refering to

brisk seal
#

so you are using SetupIntent + PaymentElement?

knotty sinew
#

SetupIntent + PaymentElement

brisk seal
#

right

knotty sinew
#

{code: 'instant_verification_incomplete', type: 'validation_error', message: 'No current account linked. Please link a current account to complete this transaction.'}

brisk seal
#

and creating the SetupIntent works, but you get an error when you try to confirm it?

knotty sinew
#

correct. something breaks when I add second payment element

brisk seal
#

and why do you need 2 PaymentElement on the same page?

knotty sinew
#

one is for card and second is for bank account. I tried to convince people that we should have single modal, but I couldn't.. so there it is

#

so I load two separate payment element with two different SetupIntents and both have set different "payment_methods" types

brisk seal
#

got it. do you have a public URL where I could reproduce this?

knotty sinew
brisk seal
#

thanks

knotty sinew
#

it's a tunnel for my localhost so if there is anything I can do there, just tell me

brisk seal
#

I managed to log in. but then I don't see any links to "account" or "payment" as you mentioned.

knotty sinew
#

"account" is on the left navbar

#

then there will be payments tab

brisk seal
#

got it, looking into this.

#

I just used the Payment Element "bank account", and it just worked with no errors

knotty sinew
#

yes, bank account works. It's a card that does not (its element is loaded first)

brisk seal
#

oh I see

#

could you dinamically mount/unmount the PaymentElement when users click on the buttons? this way it would prevent this type of conflict.

knotty sinew
#

hmm

#

ok, maybe that will help

#

I will try this approach and if it won't work I come back .. : )

#

hopefully I won't bother you anymore. Thank you, have a good day

brisk seal
#

happy to help 🙂