#yerayamenitiz_unexpected
1 messages Β· Page 1 of 1 (latest)
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.
- yerayamenitiz_unexpected, 21 hours ago, 37 messages
π 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/1273282655907221586
π Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello
As far as I know, that's all the changes you need..
Do you see it if you set `preferredNetwork explicitly?
https://docs.stripe.com/co-badged-cards-compliance?type=web-elements&ui=card-element#selecting-a-default-network
I haven't, but I want all networks available and allow the user to choose.
I understand that, I'm just wondering if that changes anything
Unless I deploy that change there's no way to verify it since in local it always displays the dropdown.
Reading through some docs, I see that we mention that CB may not fully be available until an account has processed 50 EUR from CB eligible cards. Do you know if that may apply to your account or your connected account? https://docs.stripe.com/payments/cartes-bancaires#availability
By the way, we have another place in the app where we use the Payment Element instead of Card Element, we also initialize it with "onBehalfOf" and the dropdown is not displayed either
Yes, it has processed more than 50 euros
We had that into account already
You can check here https://dashboard.stripe.com/connect/accounts/acct_1Mtl22PrVya88P7u/settings/payment_methods
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
account ID acct_1Mtl22PrVya88P7u
I think it would be best to ask our support team to look in to this on your account. We mostly can answer coding questions on this server. If CB is showing up and working in your local env, then your code is correct. It sounds like this is a restriction coming from an account configuration or CB requirement similar to the 50 EUR requirement, which our support is better equipped to look in to.
https://support.stripe.com/?contact=true
Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
I contacted them first and spent hours with them on the chat, they advised to use de hideIcon to false but didn't work.
I will try that preferred network param but if it doesn't work what do you advise me to do? Because I followed all your guidelines and it still doesn't work, I'm kind of lost and it is mandatory for us to have this working
Also according to the docs it always works locally regardless of the settings or how you init the Stripe elements, so it's not an indicator that it is working at all, it was already working locally before I started deploying your recommendations
hello
Hello!
I have a question about "Ideal" and "Bancontact" payment methods, do you have an idea about these pms ?
No idea π
@silver glen please follow instructions in #help channel. Don't jump into other threads..
Still looking in to this
Thanks π
The only requirement I'm finding so far for OBO + CB is that the connected account needs the CB capability enabled but it looks like that has been the case on that account for about a week
Do you have the ID of any payment intents that you created with OBO set to this specific account that I can take a look at?
Yes, I can give it to you give me a second
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
π can you do me a favor and retrieve that Connected Account and show me the payload for the cartes_bancaires_payments capability?
Also can you show me your relevant client-side code?
Yes
Give me a second
=> #<Stripe::Account:0x617ec id=acct_1Mtl22PrVya88P7u> JSON: {
"id": "acct_1Mtl22PrVya88P7u",
"object": "account",
"business_profile": {"annual_revenue":null,"estimated_worker_count":null,"mcc":"7011","name":"9017739300018","support_address":null,"support_email":null,"support_phone":null,"support_url":null,"url":"https://www.suites23.com/"},
"capabilities": {"card_payments":"active","cartes_bancaires_payments":"active","transfers":"active"},
"capabilities": {"card_payments":"active","cartes_bancaires_payments":"active","transfers":"active"}
client side code is a little bit convoluted because it's legacy code
but I will do my best
in parts, ordered:
const stripe = Stripe(
stripe_public_key,
{
onBehalfOf: '<%= @stripe_object.on_behalf_of %>',
api_version: <%= STRIPE_VERSION.DEFAULT %>
}
);
let elements = stripe.elements();
let card = elements.create('card', {style: style, 'hidePostalCode': true});
card.mount('#card-element');
then after this we listen to events like the "change" event on the card object
do you need more code besides this? I can send you the whole script if you want
Thank you, that is the info we were looking for. Those look like they are what they need to be for CB to show up. I see that that hideIcon property is false by default, so I would expect it to show up even if you aren't explicitly setting it.
Cool
Also is this the same account you were using to test with your test mode charges?
no, I was using another one to test in the sandbox
the account I provided is a production account from one of our clients
you can even test yourself because the page where you introduce the credit card details is public, don't make a real payment though π
this is the production client side page that renders the Stripe element for "acct_1Mtl22PrVya88P7u"
Can you share your testing page as well where this is working that we can look at?
That's only on local environment
Ah
I can make you a screenshot if you want though
It's the exact same code I assume?
exactly the same
the only thing different is the environment
one is my local env and the other is production env
K give me another minute
no problem, thanks for your time
Hmm I don't see that you have hideIcon set to false or undefined here...
I know you said you already tested that and it didn't fix it
But can you push that to your prod site here so I can see hideIcon: false is set?
Really though that is the default so it really shouldn't matter...
I can but that's gonna take some time
Because I leave in an hour and our pipeline stops deploying in 10 minutes
and I'm not back until monday
Yeah okay actually don't worry about that -- if it is working in test mode then that really shouldn't be the reasoning
Okay I do think it has something to do with the Connected Account but I don't know why
In our logs I can see isMerchantEligibleForCBC":"false"
But also isIntegrationEligibleForCardElementCBC":"true"
Mmm... Interesting
So yeah your integration is fine
I think the best next step here is to write into our Support team via https://support.stripe.com/contact/login and provide them the account and the link to your site where we can repro and ask them to look into why the merchant would be ineligible -- that part is a bit outside our purview as we just focus on the API integration side of things here.
Sorry that we can't really help more π¦
I already spent several hours with them on the chat. And provided all the information they requested.
Gotcha in that case I would just ask for them to escalate you so that this can get to our actual CBC team so they can clarify why the account isn't eligible