#paulpayen
1 messages ยท Page 1 of 1 (latest)
HI @spring skiff !
hi! I wasn't aware of this restriction to be honest. Do you happen to have a request ID req_xxx for that error?
I assume we document this limitation somewhere(like I said though I haven't heard of it before now though so I don't know directly where, but can dig with more context)
ok , let me search
req_3tCVaK2TcpoIFB
the strange bank account is ba_1KyOqQKAl5Y7KV9JHXgVsgSG
so to answer your question that's how you'd know, you have to be aware that you're using that feature of our product and encode the rules from the docs into your app
strange ...
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Can I use this ?
note that on that Stripe account, the bank account ba_1KyOqQKAl5Y7KV9JHXgVsgSG is a CH bank account
not really I think, we don't update that very well, and I don't think it has any information about this kind of restriction
I would go with "encode the rules from the docs into your app"
if we take my sample with "switzerland"
I cannot see in the doc what happens for currency CHF and EUR.
nothing special, since that's supported by default
the highlighted section(which links to the first link I posted) only applies in this case where you got the error because you're paying GBP to a Swiss bank account
yep but you are a Custom Connect platform for almost 5 years now so you likely do this a lot!
I mean your Stripe platform account uses Custom Connect, with manual payouts, and you've been had an account since 2018, so you have definitely evolved your integration over time in the past since you have a very tightly-coupled integration with Stripe's raw APIs!