#iosojn_error

1 messages · Page 1 of 1 (latest)

serene coralBOT
#

đź‘‹ Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

đź”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1457809534645960868

đź“ť Have more to share? Add more details, code, screenshots, videos, etc. below.

dry thistle
patent phoenix
#

req_41xV758QwXypGb

dry thistle
#

The payment method us_bank_account requires the Connected Account to have the us_bank_account_ach_payments capability. The Connected Account in that request does not have it.

patent phoenix
#

If enabled how long does it take to propagate?

#

I have enabled it but still get the error

#

New request id req_IUg8cnDpL2iyXL

#

Bump

dry thistle
#

You have to request the capability but then the capability has to become active. This may require collecting more KYC information from the Connected Account

#

The capability is not active for that account.

patent phoenix
#

I have enabled it now but still get the error

#

Any other tips

dry thistle
#

Sorry but I think you are mistaking the way this works with Connect. You don't "enable" the capability, you "request" it by updating the Connected Account.

#

That triggers a process where the Account is reviewed to determine what, if any, additional information we require to enable this capability.

If no more informaton is required, the capability becomse active. If we require additional information, the requirements property on the Account object will be updated to reflect this.

#

In both cases, we will emit an account.updated webhook event to notify you of the change

patent phoenix
#

Ahh, that makes sense, thanks

#

I can check the account via an api call to determine if the capability is active?

dry thistle
#

Yes! It will be in the capabilities property

#

Right now we just show the following:

capabilities: {
    card_payments: "active",
    transfers: "active"
  },
patent phoenix
#

Which property would indicate ach is enabled?

dry thistle
#

The capabilities property. It will include us_bank_account_ach_payments: "active" when this capability is active

patent phoenix
#

I do not see this property for a test mode account but i am able to create an ach account. Is there any relation?

dry thistle
#

I do not see this property for a test mode account

This property 100% exists for Test accounts. Are you retrieving the Account object via the API?

patent phoenix
dry thistle
#

i see a recent account.updated event here that includes the capabilities property in the JSON payload.

patent phoenix
dry thistle
#

Ah wait, that is for the Dashboard of the Connected Account. Regardless, the event was successfully delivered to a webhook endpoint

patent phoenix
#

I see, thanks

#

Do you know why test mode accounts do not return the property but ach creation works?

Account number; acct_1SXSGfRgyOWgvGQb

serene coralBOT
dry thistle
#

Do you know why test mode accounts do not return the property but ach creation works?

I am not able to reproduce this. When I retrieve accounts I do see this property.

patent phoenix
#

Interesting

#

This is all i see for the account

"capabilities": {
"bancontact_payments": "active","card_payments": "active","eps_payments": "active","ideal_payments": "active","klarna_payments": "active","p24_payments": "inactive","transfers": "active",

#

No ach included

#

But i am doing through the stripe shell

#

acct_1SXSGfRgyOWgvGQb

#

Can you please share the json you see?

silk oxide
#

Hello
I'm taking over for Snufkin as they need to step away

#

Can you try using the API directly via something like postman or something else? rather than Stripe Shell

patent phoenix
#

Will do, thanks

#

Tried with the sdk and the usbankaccountachpayment comes back as null aswell

silk oxide
patent phoenix
#

Will try that

#

{
"id": 
"us_bank_account_ach_payments",
"object": 
"capability",
"account": 
"acct_1SXSGfRgyOWgvGQb"
Connected account
,
"future_requirements": {
"alternatives": [],
"current_deadline": 
null,
"currently_due": [],
"disabled_reason": 
null,
"errors": [],
"eventually_due": [],
"past_due": [],
"pending_verification": [],
},
"requested": 
false,
"requested_at": 
null,
"requirements": {
"alternatives": [],
"current_deadline": 
null,
"currently_due": [],
"disabled_reason": 
null,
"errors": [],
"eventually_due": [],
"past_due": [],
"pending_verification": [],
},
"status": 
"unrequested",
}

#

It also says not available

silk oxide
#

ah it's unrequested

#

If you update it and set requested to true - does that make a difference?

patent phoenix
#

What i am curious about is why users are still able to make the ach account in test mode even though it is unrequested

#

But in live mode it doesn’t work

silk oxide
#

Yeah I'm not sure but it is possible that we just have relaxed validations on our end for test mode/sandbox

patent phoenix
#

Makes sense

#

That’s all, thanks