#liviu-iosif_api
1 messages ยท Page 1 of 1 (latest)
๐ 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/1367129466429505598
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Example payment intent creation payload
{
"amount": 50,
"currency": "USD",
"statement_descriptor_suffix": "-",
"description": "Invoice #PR5781746018220",
"application_fee_amount": 21,
"on_behalf_of": "acct_1J5BBQQdVu2h51QX",
"transfer_data": {
"destination": "acct_1J5BBQQdVu2h51QX"
},
"customer": "cus_Ona4DaxRJXw43h",
"metadata": {
"type": "patient",
"account_id": 1300,
"invoice_id": 28274,
"patient_id": 6594,
"env": "local",
"platform": "web"
},
"payment_method_configuration": "pmc_1RJaE3Hujl8GFxJCHy4jG2hH",
"automatic_payment_methods": {
"enabled": true
}
}
Hi there ๐ can you share the ID of a request you made that resulted in the error you mentioned?
The most common reason for that error is that the object you're trying to reference resides on a different Stripe account or in a different mode, but I can get a better sense of that from the request's ID (which will have a req_ prefix).
https://support.stripe.com/questions/finding-the-id-for-an-api-request
hi, rando here for a different issue, but i do see that you used on_behalf_of - if I understand correctly it's expected that any policy-like objects such as payment_method_configuration come from that ACCOUNT so like if you work like me with the CONNECT ecosystem you might need to create the profile for the connected accounts, depending on what/how you do things
this is the request id: req_JRdSTZ7ad3pkP3
I have everything set up regarding Connect and configurations.
I have Stripe implemented for 5 years already and working in this setup perfectly fine. Now I want to hide "Link" as a payment method in certain situations and I hit this blocker that I am describing.
Hm, I do think Connect may be interferring here. Normally, since this is a Destination Charge style flow, objects you reference would need to reside on your Platform account rather than the Connected Account. But I'm double checking whether that holds true for PMCs when using on_behalf_of.
First thing to try, can you try creating the new Payment Method Configuration on this page (since this is for use with Connect), and see if the error subsides if you use that PMC?
https://dashboard.stripe.com/test/settings/payment_methods/connected_accounts
Please let me know if that's the case, so I can flag to our teams that the error message needs to be improved in this case.
I did that already .
I tried with this one which is account specific: pmc_1RJaE3Hujl8GFxJCHy4jG2hH
and with this one which is for Connect: pmc_1RJa3kHujl8GFxJCk50mqyT9
The result is the same: No such payment_method_configuration: pmc_XXXXX
Neither of the IDs you shared matches the ID of the PMC for use with Connect payments based on what I'm seeing.
What Configuration ID do you see under Default if you access the page I shared a link to?
yep, another one is the default: pmc_1NAa5lHujl8GFxJCSWiTigZz
The default should remain the default and I want to reference another one for a specific case where I do not want to show Link.
Yup, do you receive the error if you use that PMC ID? I know it's the default and not what you want, but I think the page of the dashboard you're on when you create the PMC is important here. I want to confirm whether using a PMC from the page I referenced avoids the error, and if so I think you should create the PMCs you want to use for your Connect integration on that page.
yes, I receive that error regardless of which pmc_ I set in my PI request. Including the default one.
Can you share the ID of the request where you tried to use it and encountered an error? I'm not quickly spotting that in the logs.
one second, trying it again
req_NL8jJEzD9jq0IC
Weird, now it works with the default one.
Trying with the other config as well...
Did you change anything?
Looks like now it works with the non-default one as well: pmc_1RJa3kHujl8GFxJCk50mqyT9
Now I have another issue: I am trying to enable Card payments and it looks ON in Stripe, but the created payment intent does not allow card
Can you share the payment intent id
req_zwGLTMrBMyMXoz
pi_3RJbnBHujl8GFxJC0scZ5ymm
Weird
Let me check with a colleague. I noticed a different payment method config in the response is being used (where cards are turned off). Not sure offhand why
this is a new try with pmc_1RJa3kHujl8GFxJCk50mqyT9 : pi_3RJbxbHujl8GFxJC1tJVUDvC
Yep waiting to hear back from a colleague on this
Will let you know when they respond
Could be possible to put the discussion on hold and pick back up in a few days?
Sure you can open up a new thread and pick up
We don't leave threads open
I'll message here when I get a response back from my colleague though
If I do that do I need to come with the entire history? ๐
Just a brief summary of the outstanding question
Hopefully I'll have an answer for you on the above though when I hear back from my colleague
ok, thank you!
Ok I got a response on this. When you update a connect payment method config on the platform, it takes time to propagate to all the connect accounts. A bridge payment method config is created directly on the connect account as a copy of the settings from the platform's connect payment method config. This connect account hasn't had its bridge payment method config updated yet. When you make a change on the dashboard to a connect payment method config, you should see a banner that says Updating your connected accounts' settings... (X of Y completed) These changes will affect new and existing accounts. This might take a few minutes.
I see you have several thousand connect accounts in test mode
So this will take some time
I see it's still propagating actually