ameenmathers

[supple adder]

I couldn’t even update it in stripe backend

[oblique ibex]

What kind of account are you onboarding? What onboarding flow are you using?

[supple adder]

custom

I just couldn’t get it to remove the restriction.

 $customer =  $stripe->accounts->create([
             'type' => 'custom',
             'email' => $email,
             'capabilities' => [
                'card_payments' => ['requested' => true],
                'transfers' => ['requested' => true],
             ],
             'business_type' => 'individual',
             'business_profile' => ['product_description' => $category],
        ]);```

[oblique ibex]

This article explains how to collect eventually_due requirements, which should satisfy all onboarding requirements: https://stripe.com/docs/connect/custom/hosted-onboarding

Does that get you oriented in the right direction?

[supple adder]

so essentially here ```php
$account = $this->retrieveAccount($aid);

        if ($account->details_submitted) {
            $userEdit = User::findOrFail($uid);
            $userEdit->update([
                'stripeVerified' => 1,
            ]);``` i am retrieving the account to check if details_submitted, how can i check if the capabilities have been filled

[oblique ibex]

You'll have to look at the requirements hash: https://stripe.com/docs/api/accounts/object#account_object-requirements

[supple adder]

ok sure let me check

ok i just the logic

i made it check if the capabilities are active and details submitted true before it verifies a user

is there a way i can use the stripe backend to remove the restrictions on the accounts?

[gilded pawn]

Hi, stepping in and catching up.

[supple adder]

awesome

[gilded pawn]

When you say 'restrictions', what are you referring to?

[supple adder]

the connect account is restricted on the stripe dashboard

[gilded pawn]

I see, in this case, you'd look at currently_due requirements, and provide these so remove these restrictions.