#perqin_docs

1 messages · Page 1 of 1 (latest)

tender sparrowBOT
#

👋 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. Thank you for your patience!

⏱️ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime! If this thread is closed and you have another question you'll need to start a new thread.

🔗 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/1214042695115210834

📝 Have more to share? You can add more detail below, including code, screenshots, videos, etc.

tame compassBOT
#

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

fallow arch
#

I'm telling you the detail of our issue.

#

We are implementing the status badges following the documentation (https://docs.stripe.com/connect/dashboard#status-badges), but we get confused as some accounts don't match the behavior in the doc.
According to the "Enabled" section of the doc:

In the account’s requirements hash, the array eventually_due contains at least one requirement, but payments and payouts are enabled and current_deadline is empty.
So it seems that an account in "Restricted Soon" status should have its requirements.current_deadline set.
But we find an exception. There's an account in test mode, which is shown as "Restricted Soon" in Stripe Dashboard: acct_1OgJMoIpoA1b0rjs. But its requirements.current_deadline is empty. Instead, it has the future_requirements.current_deadline set.

#

Here's the partial response of the account object:

{
"charges_enabled": true,
"future_requirements": {
"alternatives": [],
"current_deadline": 1713294000,
"currently_due": [
"settings.payments.statement_descriptor"
],
"disabled_reason": null,
"errors": [
{
"code": "invalid_statement_descriptor_business_mismatch",
"reason": "Your statement descriptor must reflect your business. Change PM3 so it’s similar to your business name, legal entity name, or URL.",
"requirement": "settings.payments.statement_descriptor"
}
],
"eventually_due": [
"settings.payments.statement_descriptor"
],
"past_due": [],
"pending_verification": []
},
"id": "acct_1OgJMoIpoA1b0rjs",
"payouts_enabled": true,
"requirements": {
"alternatives": [],
"current_deadline": null,
"currently_due": [],
"disabled_reason": null,
"errors": [],
"eventually_due": [],
"past_due": [],
"pending_verification": []
}
}

#

Please help us implement the status badges correctly.

zealous glacier
#

For Restricted soon, both requirements and future_requirements should be checked

#

If future_requirements isn't completed before the deadline, the account will be restricted

fallow arch
#

Then I have another problematic account: acct_1EQDD2CgZKMc6r3y. This is a live mode account. It also has empty requirements hash, and has future_requirements.current_deadline set. But on Stripe dashboard it is in "Pending" status.
Its future_requirements field is:

"future_requirements": {
"alternatives": [],
"current_deadline": 1713294000,
"currently_due": [],
"disabled_reason": null,
"errors": [],
"eventually_due": [
"person_Eu1F86oNUMBgCC.id_number",
"person_HdRdbEOyu71lE0.id_number"
],
"past_due": [],
"pending_verification": [
"business_profile.mcc"
]
},

zealous glacier
#

The status is in Pending because there are verification reviews in the process

#

future_requirements should also be completed as shown in the response above

#

Status badge is a Dashboard only feature and I'm afraid we don't know what is the order / priority of these badges are shown

#

In any case, when requirements and future_requirements are not empty, your account should collect the information to prevent it from being restricted