#[LBG] India-account-updated

1 messages · Page 1 of 1 (latest)

latent blade
#

Hi 👋 it sounds like you're already tracking the right events, could you provide clarity on what you're referring to by the following?

the status of a Standard connected account

mild garnet
#

Hello 🙂

#

I need to know when I have to send an alert to the connected account to tell him he needs to complete information

#

Example : when the connected account has finished its first onboarding to set up company information, then the status goes to "pending" so Stripe verifies information. Then the status goes back to restricted because Stripe needs the connected_account to upload documents

#

That's the moment when I need to alert the connected_account

latent blade
#

So that's tricky to tell because the dashboard calculates those statuses, and they aren't actually stored on the Account objects. However, Accounts do have the requirements hash which lists the currently_due and eventually_due requirements, along with the disabled_reason.
https://stripe.com/docs/api/accounts/object#account_object-requirements

Stripe API reference – The account object – curl

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

mild garnet
#

There are too many information in the JSON events, which is good, but there isn't a "global status"

#

Yes that's right but it obliges us to create 168468168686 conditions

#

One way to do it is : if capabilities.card_payments == "inactive" AND previous_attributes.capabilities.card_payments == "pending"

#

Then alert the Connected account

latent blade
#

But the exact logic of when to notify an account will fluctuate from one integration to the next, so we provide the building blocks to construct logic appropriate for your flow rather than forcing you to adapt your flows to prebuilt logic.

mild garnet
#

I understand

#

What do you think about my proposal ?

#

Even if it is not really clean

latent blade
#

It's a good approach to check when the card_payments capability goes into a pending state for an account.

mild garnet
#

Do you have the conditions used by Stripe to display the Connected Account status ?

#

I guess it all goes with currently_due, eventually_due, past_due, etc

latent blade
#

No I don't, we're not terribly familiar with the dashboard in this forum. However, the doc that you linked seems to explain the criteria behind at least some of them.

Examples:

Restricted means the account has payouts or payments disabled.
So you'd be looking at capabilities.card_payments and payouts_enabled.

Restricted soon means the account has a due date for providing additional information.
Probably want to look at requirements.current_deadline and requirements.currently_due

mild garnet
#

OK checking on this, thank you

#

Do you confirm that the details_submitted is not sufficient to activate payouts : payouts_enabled ?

latent blade
#

I'd assume there is a verification period between when details are submitted and when payouts are enabled. What's in requriements.pending_verification?

mild garnet
#

You assume right

#

Can I send you a full JSON here ?

#

What capabilities a refund of a direct charge between customer and standard connected account need ?

latent blade
#

A direct charge means the payment is happening directly on the connected account, so whatever capabilities align with the payment methods that you want to customers to be able to pay with. I don't think refunds have an associated capability.

mild garnet
#

Clear, thank you

latent blade
#

Happy to help!

mild garnet
#

We are using card payments only between customers and connected account (direct charges). We can consider the connected_account able to received payments and have payouts as long as payout_enabled is TRUE and capabilities.card_payments == "active"

#

Would you agree with that ?

slender mountain
#

Hello taking over for toby here. Yes that should be the case (and as long as the account isn't showing restricted in your platform's dashboard for any reason)

mild garnet
#

Well, when the account is marked as "restricted", payout_enabled should be set to False and capabilities.card_payments == 'inactive' or 'pending' (something different from 'active'). No ?

slender mountain
#

Yep

mild garnet
#

Ok great

#

I'll run some tests

mild garnet
#

This is a screen of the first event account.updated in a connected account onboarding

#

Do you confirm that card_payment key will always be present in this event ?

copper hull
#

Hi there! Stepping in for @slender mountain as he had to step away. Catching up....