#mr_james_
rancid moat
Good question. Checking in to this
Can you send me the ID of the request (req_123) where you saw this error?
copper oasis
It was via the dashboard, I don’t think there is a request id returned in the error message
“Could not create subscription
The payment method type customer balance does not support the currency usd.”
rancid moat
Dashboard requests should also be logged in your request logs. If you try again it should show up here: https://dashboard.stripe.com/test/logs
copper oasis
The subscription is set to send an invoice and the Bank Account payment option is ticked
We have got around it by unticking the bank account option
But we need to know how to turn that option on when currency is USD as I assume Bank Account only accepts GBP
rancid moat
Thank you for the request ID, checking in to this. Our docs seem to indicate that subscriptions should support bank transfers and they don't mention a currency restriction so I think this may be possible
copper oasis
Ok thanks
rancid moat
I think that customer balance in general may only support the currencies that your account can have a bank account in. I am still trying to confirm this and will get back to you with what you can find.
copper oasis
Yeah I wondered that
We can add a USD payout bank but wanted to confirm that will fix it first
whole hearthBOT
rancid moat
Just added one to my test account and it did not resolve the error unfortunately
Still checking in to what is supported here
copper oasis
Thanks
serene gorge
Hello! After looking into this further it looks like the currency restrictions on customer_balance are quite restrictive. You would likely need a bank account in USD for this API request to succeed.
copper oasis
I think @rancid moat tried that and it didn’t work
serene gorge
Did you change the currency or country of your account at any point?
copper oasis
No
serene gorge
This might be a bug on our end. I'll flag internally, and in the meantime I recommend you write in to support with details (especially the request ID: REMOVED_PER_USER_REQUEST) so you can get a followup async.
copper oasis
Thx, are you ok to remove the request ID from your last message
We have it recorded here
serene gorge
Request IDs are not sensitive, and I'd like to keep it here in case someone else on my team refers to this thread later. It already caused a delay when I picked up this thread and the request ID was removed.
copper oasis
I understand but would prefer it to be removed please
We can close this case, I will contact support
serene gorge
Removed.