xaositect_webhooks

[alpine stratus]

👋 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/1297975423917096962

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[craggy raven]

Hello

[oak geode]

Howdy

[craggy raven]

So to clarify, you expected based on this capability.updated Event that the account was fully enabled but that was not the case, correct?

[oak geode]

correct

[craggy raven]

Gotcha, yeah the recommended Event type to listen to here is actually account.updated

That Event can let you see anything that is outstanding in the requirements hash

And it will fire alongside capability.updated but with more information

[oak geode]

we are listening to that as well

I think this was the event evt_1QB1Lp2Ym3KhdAfuXC4KMYuT

most recent for them

"requirements": {
"alternatives": [
],
"currently_due": [
],
"errors": [
],
"eventually_due": [
],
"past_due": [
],
"pending_verification": [
]
},

and we are checking the reqs hash off that event as well

oh wait further down:

    "requirements": {
      "alternatives": [
      ],
      "current_deadline": null,
      "currently_due": [
      ],
      "disabled_reason": "listed",
      "errors": [
      ],
      "eventually_due": [
      ],
      "past_due": [
      ],
      "pending_verification": [
      ]
    },

[craggy raven]

Gotcha let me take a look

[oak geode]

Okay that's interesting there are two requirements hashes in the event

So it seems like there's really nothing for the user to do here, but instead of calculating whether or not they can receive payments off of whether there are currently due requirements, we should be checking payouts_enabled?

[craggy raven]

Yep that's correct.

The most holistic parameter is charges/payouts_enabled.

[oak geode]

Thanks for the advice, I appreciate it

[craggy raven]

And then the requirements hash should have more details

[oak geode]

Sadly not really, just 'disabled_reason: listed. Still that's better than nothing.

[craggy raven]

Well yeah but that is more than nothing is what I meant

[oak geode]

Agreed!