#gilberto-account-verification
1 messages ยท Page 1 of 1 (latest)
Looks like this is possible in the Dashboard, looking in to the API... https://stripe.com/docs/connect/pausing-payments-or-payouts-on-connected-accounts
I know payouts can be restricted
But it's not payouts... it's charges, or Transfers
If I pause the payout the user cannot move that money out of Stripe... but we can still Transfer them money!
which is what we want to test
that we cannot transfer them money once charge_enabled is back again to False
Right, that doc is about pausing payments as well
Not seeing a way to update this in the API
Will double check with my colleagues about this
As far as I know this cannot be updated directly via API
But I don't really know I want Stripe confirmation
Also I see this
No payments option
Yeah looks like this is dashboard only
If you are using a flow where you create the PaymentIntents you can just change your code to not create the intent
Can also update radar rules
Isn't your platform initiating that via an API call?
Yep
You can have a list of accounts you don't transfer to and check that before creating one
stripe.Transfer.create(...)
Unfortunately there isn't a programmatic way to block your transfers like that immediately such that the Stripe API just errors out
Yeah the thing is QA (you know QA ๐) need to:
- Create Account
- Transfer account, getting error due charge enable is false, not configured
- Configure Stripe, charge enable to true
- Transfer an account, everything good
- Retrisct that account
- Confirm that no Transfer can be done to that restricted account
- Enable account again
- Transfer account again as first time
We are on step 5
If I use the unsuccessfull SSN it says it's going to be restricted in 15 days
I just want it to do it sooner
๐
What @signal kayak says about ๐ฅบ
To clarify, you can't disable the transfers more quickly via the API. I'll double check if pausing payments or payouts would do that but you would have to manually do it via the API
I mean doesn't matter If I have to pause it through dashboard or API
I updated the steps to clarify
In which one we are
Ah apologies, I did not fully grasp your screenshot. So it looks like those dashboard actions do not disable transfers. So making code changes to not make transfers to restricted connect accounts would be the only way to do this
I mean if the account is really restricted Stripe works well, the Transfer is not going to work
which is what we expect!!
gilberto-account-verification
the thing is in order to really restrict that account we have to wait 15 days
And idk if we can do something else to pause it sooner
I don't think we have a specific/easy way to test transfers being disabled today so that's not really possible sorry
(removed the picture since it takes half the screen of the conversation)
thank you for your patience guys, can you please elaborate something to give an answer to QA and Product? and tell this is not possible
And that we have to wait 15 days to restrict an account again
Not really sorry. I don't fully grasp what you are trying to do unfortunately. But there's no way to simulate transfers working and then not working again
I think is just that... Transfer cannot be done on a destionation account that has charge_enabled on False
We test it when the account is initially created and good, Transfer cannot be done. We set everything to update charges_enabled to True and then Transfers works
So we just want to move charges_enabled again to False
To make sure Transfers cannot be done... again
I understand, but that's not really possible to test this once the charges have been enabled by going through verification
I checked this
https://stripe.com/docs/api/account/reject
Returns an account with payouts_enabled and charges_enabled set to false on success.
This is exactly what I want but... I can "unreject" it after that?
no you can't unreject, so it's not what you want in that case
yes... you're right
well I guess we just wait 15 days
and If that work I promise I'll be here again so you guys can know in case someone in the future asks the same
Really my advice is to test completely differently and mock the API to simulate various states, not relu on the real API and wait 15 days
Thank you, you have some doc when I can read about this?
Although QA likes to manual-test on staging environment as if it was production
no I don't really have docs for this sorry