#atob-yash_api

1 messages Ā· Page 1 of 1 (latest)

young mesaBOT
#

šŸ‘‹ 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/1283841865774403604

šŸ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

inland sluice
tepid condor
#

I have not, can I try it quickly while I have you with me/

inland sluice
#

Sure thing!

tepid condor
#

Is there anyway I can do it on the UI?

#

I'll need 2 minutes to spin up a shell in my prod env

inland sluice
#

I'm not sure if you can do it in the Dashboard or not, we're more focused on the API and code here. There might be a way to do it if you view the Dashboard as the connected account.

#

You can do that by going to the list of Connected accounts in your Dashboard, clicking on the connected account in question, then click on the ā€¢ā€¢ā€¢ button in the top right and choose the View Dashboard as this account option there. Then look around for a way to enable that capability.

tepid condor
#

Tried this:

  'acct_1MGodPR4bjuRAmjQ',
  'card_issuing',
  {requested: true},
  {api_key: ""}
)
#

Got this response:

#<Stripe::Capability:0x4b8ac id=card_issuing> JSON: {
  "id": "card_issuing",
  "object": "capability",
  "account": "acct_1MGodPR4bjuRAmjQ",
  "future_requirements": {"alternatives":[],"current_deadline":null,"currently_due":[],"disabled_reason":null,"errors":[],"eventually_due":[],"past_due":[],"pending_verification":[]},
  "requested": true,
  "requested_at": 1671476665,
  "requirements": {"alternatives":[],"current_deadline":null,"currently_due":[],"disabled_reason":"rejected.inactivity","errors":[],"eventually_due":[],"past_due":[],"pending_verification":[]},
  "status": "inactive"
}
#

But no change on the UI

inland sluice
#

What are you seeing in the UI? Can you share a screenshot?

tepid condor
inland sluice
#

Hm, it could be that the change will take a few minutes to propagate. If it still says inactive in a few minutes you'll probably need to reach out to support to have them get it working again.

tepid condor
#

But you're certain that re-requesting this capability is enough?

inland sluice
#

Nope, not certain. šŸ™‚

tepid condor
#

Because I'd expect to see some form of "pending" if Stripe was processing it

inland sluice
#

Support will know for sure what the right next steps are.

#

Yeah, if it does change to pending in a few minutes it should be fine, but if it doesn't reach out to support.

tepid condor
#

Sounds good, thank you!