#deepstitch - External Account Balance

1 messages · Page 1 of 1 (latest)

alpine gale
#

Hi 👋
I do not think we can check the balance on an external account without attempting a charge.

tepid void
#

got it - but, is this to say that when attempting a charge we can capture the balance before finalizing it?

rugged gazelle
#

I think he means that a charge can be initiated, and it will succeed or not based on available balance - in general, there are privacy issues without getting considerable more permissions from a customer

#

A charge would not return an account balance

tepid void
#

Makes sense. When recently attaching a bank account, the user was presented with a screen that said the platform would have access to account balances (oauth)

rugged gazelle
#

I will note I have seen some "financial accounts" beta mentioned in the help documents - you may want to check with support about that.

tepid void
#

we want them to be assured that we can't know or see their account balances during processing of transactions

rugged gazelle
#

Well, "Stripe", or at least the generalized processing systems, will have some access - or how would they authorize? - but it isn't passed to you by default

tepid void
#

got it - yes, that makes sense. we'll just need to communicate that to our clients that, although it says that this information would be made available to the payment processor, the platform doesn't see it

#

this is what they see

rugged gazelle
#

hm - that's not a flow familiar to me (NOT with Stripe)

tepid void
#

this is the screen that comes up after choosing the account in the stripe "add bank account" flow

rugged gazelle
#

That sounds like the Beta I mentioned...

tepid void
#

ok

#

I'll contact support - our clients (who use our platform) have customers that inquire about what they're allowing them to see

rugged gazelle
#

That, specifically, would open a lot more information - hence all the verification and confirmation. What are you trying to accomplish?

#

Ah, your connect accounts?

tepid void
#

exactly

#

we want our connect account holders to be able to assure their customers that they aren't allowing them to view things they don't want them to see

rugged gazelle
#

Depending on your chosen flows (especially the newer ACH flows) you wouldn't be collecting the account info in that way, necesssarily

tepid void
#

i just implemented the new flow using setupintents and the like

#

followed all the developer guides to implement this way. it works perfectly

rugged gazelle
#

That flow, specifically, does actually expose all the mentioned info - that's pretty much the point of that flow

tepid void
#

this flow allows us to get away from Plaid and microdeposits

#

thankful for it

rugged gazelle
tepid void
#

yes, exactly

rugged gazelle
#

Do you need that flow? you can accept ACH payments via the setupIntent and paymentIntents without that flow

tepid void
#

maybe i was mistaken

rugged gazelle
#

If just accepting payments, I wouldn't use that particular flow. It's intended purpose is to offer extended financial services

#

...hence asking for the extended permissions and info

tepid void
#

locating the stripe guide i'd used previously

#

this is, essentially, our exact implementation

rugged gazelle
#

Are you also following the If you want to access additional data on an account, sign up for Stripe Financial Connections. portion?

tepid void
#

lol - i was just about to mention that

#

we didn't pay attention to the fact that we can customize what information is requested

#

we'll modify the process to exclude account balances

rugged gazelle
#

That part is optional, and what I think [reminder: (NOT with Stripe)] is asking for all that extra

tepid void
#

Thanks for the insights. We'll circle back to the code and make the mods

rugged gazelle
#

if you need the assurance of available balances (rather than trust the customer and deal with the failures if any), then yeah, you'd have to get the extended permission. It's a business logic choice at that point