Have you explicitly declared which payment methods are allowed to be used in your script? Maybe if you haven’t declared anything the browser just infers it somehow, and Firefox and Chrome might have a difference in inferring default value
So maybe FireFox use the first one
and chrome the second..
I've just found
::: spoiler payment_intents.payment_method_types
The list of payment method types (e.g. card) that this PaymentIntent is allowed to use.
"payment_method_types": [
"card",
"link"
],
:::
Now I have to found the complete list of the accepted string of payment_method_types if somebody know where they are laying , let me know, because I can't find them..
Are you actually trying to use apple_pay, or it that just an irrelevant error you’re not expecting?
No, like I said, apple_pay is disabled ( willingly ) in the stripe dashboard, so I don't know why the error mention even apply_pay...
Firefox... Did you actually go through the entire process, and eventually received your payment?
yes ! I mean under the testing environment, so with the test secret key etc.. The Strip API and dashboard show the related transaction as successful...
Cause it would seem kinda weird as well if the Stripe dashboard says apple_pay is not enabled, but apple_pay does work…
That why I'm surprised !
Are you targetting the same Stripe account...
Of course I change nothing beside the visitor browser..
The link worked, Thanks a lot for the share !!
under H.264 it's ::: spoiler written... Digital Video Recorder
hummm I don't think that will help :D :::
humm files.catbox.moe seem down at the moment....
Thanks ! I guess to connect to it it's trough RJ45\ HTTP ?
Thanks @isolatedscotch@discuss.tchncs.de
I will do the first one (Blue) the second one it's indeed seem like a model number. but I've search it searx.space but found nothing..
Thank you ! I didn't think about it !
So I have tried with
payment_method_typesand it works flawlessly under Firefoxbut still not working under chrome

So it might be because of the cross-site cookies ? Do I have to change something ? or Stripe ? Thanks.
Indeed it's what I'm thinking too.
Actually I'm using the payment_intents with it's attributes automatic_payment_methods That state in it's description two contradictory thing
So maybe FireFox
I've just found ::: spoiler payment_intents.payment_method_types The list of payment method types (e.g. card) that this PaymentIntent is allowed to use.
:::
Now I have to found the complete list of the accepted
stringofpayment_method_typesif somebody know where they are laying , let me know, because I can't find them..I guess there is out there some Lemmy haters :)
Hoo ok, that indeed better.
Thanks for the precision.
because I see in the Stripe Dashboard & API call that the transaction is successful...
No, like I said, apple_pay is disabled ( willingly ) in the stripe dashboard, so I don't know why the error mention even apply_pay...
yes ! I mean under the testing environment, so with the test secret key etc.. The Strip API and dashboard show the related transaction as successful...
That why I'm surprised !
Of course I change nothing beside the visitor browser..
Thank you @Ategon@programming.dev
It's that so much CSAM[^1] that all posts with a picture need to be censored automatically ? I'm amazed if it's the case.
FYI: in Lemmy, an user can block another user ! (do not see it's bullshit content, and maybe report to admin and authority the content)
I'm not a huge supporter of automatic censorship...
[^1]:Child Sexual Abuse Material