#jyee

1 messages · Page 1 of 1 (latest)

idle patrolBOT
olive elbow
pallid peak
#

for example, if i had the account.id from an account.updated event, can i use that id to hit an endpoint to get the verification status?

olive elbow
#

Above Account Retrieval API should work

pallid peak
#

what on the account object is going to give me the verification status?

#

the "verified", "unverified" value

olive elbow
#

Do you mean you want to check whether the account is ready to process payment?

pallid peak
#

no, we are using StripeConnect to verify KYC informatin

#

so i'm listening to account.updated events, but on account, there doesn't seem to be a field that flags if the account is verified (like it is on the Person object)

#

Do i need to infer based on an empty requirements.currently_due and requirements_eventually_due being empty?

#

to clarify, we need to know if an account is ready to use a charge card product

olive elbow
#

The steps will be:

  1. Check charges_enabled to check whether the account is ready to perform live charges: https://stripe.com/docs/api/accounts/object#account_object-charges_enabled
  2. Check payouts_enabled to check whether the account is ready to accept payout: https://stripe.com/docs/api/accounts/object#account_object-payouts_enabled
  3. If requirements.currently_due field is not empty, you should bring customer back online to complete the payment. Only when requirements.currently_due is completed, then charges_enabled and payout_enabled will become true
  4. If ``requirements.requirements_eventually_duefield is not empty, bringing customer back online as soon as possible will preventcharges_enabledandpayout_enabled` to become false
#

You shouldn't need to check the verification status field specifically. requirements, charges_enabled and payouts_enabled field should be sufficient to determine whether a connected account is ready to perform charges and payout

pallid peak
#

👍