#laeti1651-cartesbancaires

1 messages · Page 1 of 1 (latest)

north matrixBOT
loud trench
#

Thanks for the info, checking in to what is happening with these payment intents and payment methods and will get back to you

loud trench
#

Apologies but this is still taking a bit to figure out. It looks like the Payment Element may not support card brand choice at the moment but I am still confirming.

I'm seeing the same behavior of Cartes Bancaires showing up without changing my settings and of it being the default brand chosen from Payment Element confirmation. I am trying to get more info on this than what is in the doc but I am having a bit of trouble finding it.

uncut sedge
#

Ok, thanks a lot 🙂

loud trench
#

CB is expected to be the default card network when it is available after it has been activated. The doc doesn't explicitly spell that out but at least that part is expected behavior so far. I am still not sure how CB was available as you don't have it turned on in your dashboard settings.

uncut sedge
#

Ok, thank you for that information. Another question is how is it possible to have 'cartes_bancaires' network when the payment method has only 'mastercard' in its networks.available ?

loud trench
#

Unsure of that as well. I'm still having trouble, I will consult my colleagues on this and get back to you with what I can find.

uncut sedge
#

Ok thank you very much !

north matrixBOT
loud trench
#

So unfortunately card brand choice with the payment element is definitely not available at the moment but we are working on it. If you write in to our support team they can help make sure that you are enabled for it as soon as it is available https://support.stripe.com/?contact=true

#

Still looking for answers on why it was an option at all despite your connect PM settings and only mastercard showing in the available networks hash

#

Are you already using confirmCardPayment for your client-side confirm calls? I see from your logs that a PaymentMethod is created with the Payment Element and then using that in a confirm call. That confirmCardPayment call is definitely a viable way of passing on the user's choice though you would need your own UI to let them choose.

north matrixBOT
uncut sedge
#

Ok, but even if the user can't choose the card brand yet, can I choose it by giving payment_method_options.card.network to the payment intent ?

I am using confirmCardPayment for one part of my client-side confirm call, but all I want to do is using cartes_bancaires everytime it is available on my users' cards.

loud trench
#

By cartes_bancaires should be used whenever it is available. You may want to enable Cartes Bancaires in your connect Payment Method settings (which currently have CB turned off though I can't confirm if that is what the setting was when pi_3NdbCJA69XfgDO9E0rJZPS8l was created).

You can pass that parameter when creating the PaymentIntent but our API will only accept if if you are also confirming the PaymentIntent with that create call. So the easiest place to add this parameter in your current flow would be the confirmCardPayment call

uncut sedge
#

I can't enable Cartes Bancaires without asking your team, and I never did it, so it was disabled when this payment intent was created.

Ok but I also need to have it in the part where I use confirmPayment, so I can't do it in this flow ?

loud trench
#

Unfortunately the confirmPayment flow does not support card choice at the moment. I would reccommend reaching out to our support to ask about being enabled for card choice with the payment element. It is not currently available but they may be able to make sure you are enabled for it as soon as it is available.