#joonasm-BNPL-Payment-Element

1 messages ยท Page 1 of 1 (latest)

winged aspen
#

Hi there!

#

Can you provide a request ID for that error?

uneven yew
#

req_E27D5Wxg4KVP05

winged aspen
#

Thanks, taking a look

uneven yew
#

we've tested with several addresses... I couldn't find any further insight in the docs

winged aspen
#

Did you test in testmode?

uneven yew
#

yes

winged aspen
#

Can you provide one of those request IDs as well?

#

Ah wait

#

Err yeah, nvm, a testmode request would be helpful as well.

uneven yew
#

ok, let me try to find one

winged aspen
#

Ah wait

#

I don't think we support Affirm on Payment Element yet

uneven yew
#

easier to create a new one evt_3Lctp5JYdUbtOnPn1r4Kj5q3

#

well that's strange... why is it in the automatic payment methods and all the docs then? ๐Ÿ™‚

#

and works in test mode

winged aspen
#

Yeah it is supported on Checkout. But I thought we hadn't released for Payment Element yet. Give me a sec though

#

Okay ignore me

#

I'm stuck in the past ๐Ÿ˜…

#

We definitely do support it

uneven yew
#

stop living in the past

winged aspen
#

Good to hear that it works in testmode

#

Let me look into the livemode case more

uneven yew
#

yeah it's strange as afaik we just pass the same data to the payment element regardless of the payment method.. and the data looks just fine

winged aspen
#

And you stated you tried another address as well and are seeing the same thing in livemode?

uneven yew
#

yes.. with any address

winged aspen
#

still looking just fyi

winged aspen
#

Okay so seems like this has to do with communication that is happening upstream. We will need to reach out to our partners to get more details. Can you write an email to our Support team (https://support.stripe.com/contact/login) and provide a short summary with the request IDs and mention my handle bismarck in the email and let me know when you have sent it?

#

Then I can grab the ticket and follow up over email

uneven yew
#

Ok, will do. Thanks.

uneven yew
#

ok, sent