#jonathanhuang13
1 messages · Page 1 of 1 (latest)
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.
- jonathanhuang13, 3 days ago, 57 messages
- jonathanhuang13, 5 days ago, 22 messages
Hi there! Pretty sure this depends on the customer location. We mention some of this here: https://docs.stripe.com/payments/payment-method-messaging#dynamic-display
Hi thanks for the reply. Klarna does depend on the location/currency but it looks like even if the location is US and the currency is USD, the messaging element won't display if the price is >$1000 even though Klarna does support prices >$1000
Hi, stepping in. Depending on buyer location and the amount of the purchase that is expected.
Hey yeah I realize but I'm saying that I have a case where the buyer location and amount is supported by Klarna (i.e. I can go through the Klarna flow and make a purchase) but the messaging disappears
Yeah, so depending on that specific information, it is expected that the messaging disappears. Like, depending on the amount for the same location, that message can disappear. It is all expected.
Sorry I don't think that's expected. Why would the messaging disappear if in the PaymentElement, Klarna still shows up as an option and I can click on it, go through the flow, and purchase the item?
I was able to confirm with with internal resources. This is how it works.
Can you say more as to why? It's inconsistent with what's showing up on the PaymentElement, which really shouldn't be the case
It's just built this way, there is not much more to it.
Then where can I submit a bug request because this seems like a bug
This is not a bug, but you can write in to support: https://support.stripe.com/contact as a next step.
Although I see how it can look that way
I reproduced it on my own, and then confirmed internally to be 100% sure
Okay wait, can you explain why it's not a bug then? Because the PaymentElement showing inconsistently from the MessagingElement does seem like a bug