@L4r4 - eviltoast
  • 7 Posts
  • 13 Comments
Joined 9 months ago
cake
Cake day: February 20th, 2024

help-circle











  • 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

    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

    1. Settings to configure compatible payment methods from the Stripe Dashboard
    2. Automatically calculates compatible payment methods


    So maybe FireFox use the first one and chrome the second…

    I’ve just found

    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…