#BeardMan-retrieve-bankaccounts
1 messages · Page 1 of 1 (latest)
Hi there 👋 do you see the desired accounts if you try retrieving them through our sources endpoint?
https://stripe.com/docs/api/customer_bank_accounts
Hi @stuck idol, thanks for the response - yes I did. I've tried that, but I keep running into the following issue:
invalid_request_error
more_permissions_required
Error
The provided key 'ek_test_YW***..***AzHc' does not have the required permissions for this endpoint on account 'acct_xxx'. Having more permissions would allow this request to continue.
I figured I did something wrong as the endpoints were different, but it seems there is another problem somewhere else 🤷
Keep in mind, using the exact same setup i.e. same key, API key, customer key, etc (calling another endpoint) I get my cards in the same session, but when requesting bank accounts the error shows above
You'll need to retrieve this using your secret key from your server, not with an ephemeral key from the client
Can you share a request ID for this? eg req_123 https://stripe.com/docs/api/request_ids
sure, sec
@ocean egret sorry for the delay
req_ry062qeKS3pmCy
I hope it is just a small oversight on my end
Ok thanks for the sample -- getting some help looking at this 🙂
@ocean egret many thanks!
@charred orchid Just to clarify, has that call ever worked before for you?
@potent raft nope
I was only able to get cards, never been able to get bank accounts
there is a test ACH account added to the customer query, all in a test environment
gotcha, so I think it's simply that today, we don't support retrieving those today. You'll want to report this to our support team: https://support.stripe.com/contact instead. I'll flag too
@potent raft wait, so you are telling me that a client can add an ACH account, remove it but not get a list of ACH bank accounts?
Android native allows that
what does "Android native allows that" mean? I did ask if you had a successful call before
no one makes this call today with an ephemeral key, I just checked
These are all test accounts, so I don't mind sharing this. All those highlighted I can get using
/payment_methods?type=card but there is no type=bank_account ****
that is not a screenshot from the Android SDK, that's the Dashboard
@stuck idol mentioned something about getting the secret, does that play a part in getting the ACH accounts?
the secret of what? I'm sorry I don't follow you
@potent raft sorry, wasn't Toby
okay so that is about your Secret API Key
if you use the Secret API key that call will work
ok, so I noticed using stripe-cli that I can view any customer's ACH bank account, as well as on the dashboard. That leads me to believe that a customer (i.e. someone using an app) can't view their accounts due to some "permissions" (i.e. "...need more permissions").
Do I need to handle all this on my back end, where I have this API key stored?
ACH is legacy, we haven't yet rebuilt it on PaymentMethod. So yes for now you need to use your Secret API key server-side
There's really no reason for you to ever use Ephemeral Keys outside of Mobile SDKs
gotcha, thanks @potent raft, feels like alot of extra work to be a mitm for managing bank accounts tbh
I don't really understand what you are building though and why you're even using ephemeral keys though
hmm, maybe if I can explain it will make things easier
ultimately none of that is possible, you would proxy via your server like you do for most objects you surface client-side
My app requries in app (automatic) payments based on usage/interactions of users. 2 sets of users: users, partners. Users pay via cards, partners can get paid via cards or bank accounts. Since release is only in the US, ACH accounts should suffice?
The card payments, payouts seem relatively straight forward, but being able to add, edit and remove ACH accounts is what I'm struggling with
hence my question
I'm totally lost sorry
you say "users can get paid". What does that mean? Like they receive money? If so using ACH Debit would never work
@charred orchid friendly bump
Hi @potent raft, sorry I didn't get back sooner. ACH Debit will be the recipients. i.e. (from partner POV) Add my bank account where funds from somewhere will be placed into my account
Use case:
User: Make purchase/buy service, pays amount via credit card added to Stripe
Partner: Receives payment from user to attached card / ACH account
no worries, thanks
If your goal is to PAY these partners to their back accounts, this wouldn't be something you do with Customers that have attached ACH Debit accounts. You'd have each of your partners set up a Connect account that has an attached bank account that they can they pay their funds out to
ah right, I read about that. It said the Connect accounts allow almost immediate verification, but on another SO thread someone said Conenct is required for anti-fraud/phishing, etc which made me wonder why Connect was first optional (i.e. faster verification) but then later required for transfers, etc.
@azure rose Okay, so upon e.g. Partner account creation and they add a bank account, there is an API I can use to invoke the "connect Connect to Bank Account" process right? If so, got any documentation on that?
Depending on the Connect account type the flow would vary - for Standard and Express account, the account holder manages their payout accounts and would add them through our onboarding/dashboard UIs. For a Custom account you can create an external account for them through our API (https://stripe.com/docs/api/external_account_bank_accounts/create)
ah, that makes more sense. Do you have more info I can read about this please (sorry, just want to be sure and eliminate any further confusion from my part)
Say a partner has a US bank account, then they add their bank info, on the backend Stripe Connect is attached and verifies their account. At this point (I'm not sure the account type here, I assume standard), they can manage their own payouts. For both Standard and Express, can I "manually" invoke payouts via a backend API e.g. in-app they say "Pay Me" and I pay them sort of deal?
@charred orchid is it okay for us to say you should pause and read the docs thoroughly?
Connect is a really complex product, you were mixing up payments and Connects so you likely want to spend an hour reading through our docs
I went through ACH section, I have to be honest not too much made sense
I'll go through ACH section in tandem with Connect
ACH is entirely unrelated to Connect
ok, gotcha
https://stripe.com/docs/ach is purely for debiting someone's bank account for payments.
so not used for payouts i.e. pay to, it is only used as pay from?
correct that docs is entirely unrelated. You should ignore it completely since you have no plans to debit someone's bank account for payments
awesome, sounds good
what section do you recommend I review/look at to make payments to bank accounts?
I assume that is where Connect comes in?
ah, wonderful
https://stripe.com/connect
Pay out users quickly and reduce operational overhead with Connect’s global routing and payout engine.
@potent raft thanks for the assist
my last question:
a loop back to the original, managing these "bank accounts", there is API's for that, etc?
It depends on your integration that's what Karbi explained. Connect is a really advanced and powerful product with dozens of features and some of them are available only to some integrations. You first need to decide what type of accounts you'll use which is based on what type of experience you want to give your users and what type of risk/liability you won to own as a business. This is a really complex decision
okay, I need some documentation on that specifically, got any links for me to review?
please note, this is all knew to me, so apologies for the noob questions
It's all good, it's fine to ask, but I can't really answer the next 200 questions because you didn't read the docs though
you just found docs, quoted one sentence and then stopped
This will take you at a minimum an hour to read through
hmm, okay, cool - I'll get started
https://stripe.com/docs/connect please carefully go through the docs
thanks for all the help!
will do
awesome!