#pistonmaster_unexpected
heavy fjordBOT
👋 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/1373883180171399230
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
leaden burrow
Can provide a screenshot later if necessary. It just looks like the standard shipping element and payment element, but without the billing is same as shipping button.
faint finch
I think I know what you are asking, but could you still provide the screenshot? One for the regular AddressElement+PaymentElements with button, and one for AddressElement+CustomCheckout without button
leaden burrow
Here a screenshot of my custom web elements ui that's a checkout in ui_mode custom.
Right now my workaround is to manually add a billing address element, but this looks worse than hosted checkout.
I know it exists in the code because I can (sorta?) force trigger it to open in react dev mode using hot-module refresh. by setting fields: { billingDetails: {address: "auto" }} on the PaymentElement. However that button disappears on a standard render. (Without hot reload happening)
And here is the UI in a stripe hosted checkout
That should be all.
faint finch
Yeah thank you
I think this is a limitation on the Checkout / custom ui. But let me dig around our internal logs a little bit
faint finch
Alright I can confirm this is our limitation. Will forward your feedback! Thank you for reporting
leaden burrow
Alright thank you! Hope this can be improved with a future release.
Is there some other place where I could send in feedback about some features? I may have two other things I wanted to report. (Broken logo in emails and the "acceptedcountries" forced to a single country not being displayed unlike in hosted checkout.
Or should I just open two more threads
faint finch
You could send email to support, or simple just tell me here. I will make sure they are recorded
leaden burrow
In the image here you can see it says "Germany" greyed out in the shipping address elements. (Because I set allowedCountries to just ["DE"], which requires it to only be germany. This displays that it's forced to be germany.
faint finch
Okie
leaden burrow
In the web elements however no such "forced option" is shown. (It has the same settings)
However I know the UI only accepts germany because the billing address field shows a country dropdown. (Where you can put any country)
Had to manually say it in the header.
This shows it better (I added the billing element too)
top is billing, the one below that is shipping, which is forced to germany, but doesn't display.
ig stripe could fix it by still rendering the dropdown, but setting it as disabled. SO it looks like in hosted checkout.
faint finch
To clarify, this shipping section, is it an AddressElement?
leaden burrow
yes it's the AddressELement in shipping mode
faint finch
Ah alright
leaden burrow
it knows the allowecountries as well already because it does not show a country selector unlike the billing element where any country is allowed
But it's just not displaying hat the country is forced to DE. Unlike in hosted checkout.
faint finch
So if customer click into it, it only show 1 row?
leaden burrow
It'll use the google maps selector and expand, however be forced to accept only german addresses:
Here is how it looks with the billing element that accepts any country:
There's the extra row with the "country or region" selector.
The shipping element does not show it because I put allowedCountries: ["DE"] when creating the checkout
faint finch
wait, so you have both a shipping elements and then a billing elements (like 2 Address Elements with 2 mode?)
leaden burrow
yes, that's the only way I can collect them currently (Because there's no billing address is the same as shipping address button)
This is how the whole thing looks:
faint finch
Um I think you would want to implememnt one custom field yourself instead, with a disabled dropdown. That would looks cleaner
But I understand what you are saying!
leaden burrow
I guess I could do that, but that would look weird. (Because my dropdowns have a different style to stripes)
Maybe could check out that ui library stripe has...
I also think I can't really inject into the address element to be right at that place, so just stripe showing it like on hosted checkout would be better.
(If I enable internation shipping, which has different shipping rates, it will show a country dropdown there in the shipping element)
leaden burrow
yeah it kinda bugs me that hosted checkout has it, but not web elements in checkout mode lol
If stripe web elements showed the greyed out dropdown with just "Germany" if there is only a single allowed country it'd be great.
I have one last thing I wanted to report. Payment receipt emails have a broken company logo when using https://gmx.net
With GMX:
With Gmail:
Something is wrongly formatted there with GMX, would be cool if that could look the same on any email client.
leaden burrow
GMX is a free mail service site (popular in germany)
it's an alternative to Gmail
I could also try contacting them I guess if this isn't fixable from stripes side.
faint finch
Yeah I have no idea about that. Searched internal but we don't have similar reports
Sorry
leaden burrow
Alright. I'll try contacting them then.
Otherwise really happy right now with the checkout session with web elements. Had to migrate because stripe hosted checkout has an illegal "pay" button. (Apparently meta had to pay fines because their buttons were not clear enough)
Had to make sure the button says "Zahlungspflichtig bestellen", which means "order with obligation to pay". Since it has to convey that clicking it creates the purchase contract & does the payment.
On 8 February 2024, the 20th Civil Senate of the Higher Regional Court of Düsseldorf granted an injunction action brought by the Consumer Center of North Rhine-Westphalia against Meta Platforms. The court ruled that Meta's ordering process for its paid, ad-free use of the social networks Facebook and Instagram was in violation of consumer protection regulations. The court ruled that the "Subscribe" and "Continue to payment" buttons did not sufficiently indicate that a subscription contract with a charge would be confirmed upon clicking. The court held that companies have a legal obligation to label order buttons with clear wording, such as “order with obligation to pay”. The judgement is final and enforceable.
https://digitalpolicyalert.org/event/17641-ruled-public-lawsuit-against-meta-platforms-ireland-limited-regarding-order-button-labelling
Maybe stripe could look into letting users change the hosted pay button text to stay compliant with rulings on this case.
faint finch
Uh-oh I haven't never seen this. Thank you and will forward this feedback as well
heavy fjordBOT
modern jacinth
FWIW, you could potentially use the custom text functionality with hosted to remain compliant
