#leo_api
1 messages ยท Page 1 of 1 (latest)
๐ 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/1488629930190180593
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- leo_api, 2 hours ago, 14 messages
A bit more details:
Here's the POST payload of the request (req_Rhp7bCKOO83UiC) creating the account acct_1TH4R5GE8MjFzlyI :
{
"business_profile": {
"annual_revenue": {
"amount": "500000",
"currency": "EUR",
"fiscal_year_end": "2025-12-31"
},
"estimated_worker_count": "7274",
"mcc": "5598",
"name": "match_name_relationships",
"product_description": "Lorem ipsum dolor sit amet, consectetur adipiscing elit.",
"support_phone": "0000000000"
},
"business_type": "company",
"capabilities": {
"card_issuing": {
"requested": "True"
},
"transfers": {
"requested": "True"
}
},
"company": {
"address": {
"city": "City",
"country": "BE",
"line1": "address_full_match",
"postal_code": "2600",
"state": "State"
},
"name": "match_name_relationships",
"phone": "0000000000",
"tax_id": "222222222",
"verification": {
"document": {
"front": "file_identity_document_success"
}
}
},
"controller": {
"fees": {
"payer": "application"
},
"losses": {
"payments": "application"
},
"requirement_collection": "application",
"stripe_dashboard": {
"type": "none"
}
},
"country": "BE",
"email": "demo@example.com",
"external_account": "btok_be",
"settings": {
"card_issuing": {
"tos_acceptance": {
"date": "1774971755",
"ip": "127.0.0.1"
}
},
"payouts": {
"debit_negative_balances": "True"
}
},
"tos_acceptance": {
"date": "1774971755",
"ip": "127.0.0.1"
}
}
Also is attach the value of the connected account.
Monday, I didn't have any issue and my code was working since at least 6months.
Hm can you share a request from Monday where this worked so I can compare?
Here you go for the account acct_1TGiM75UQIDCNGrM, created Mar 30, 2026, 6:07:59 PM CEST:
req_7uDpFh42BUQuCqcreation of the accountreq_2CULVUySwwRNbOcreation of the person related to the company (the representative)req_XoNw3Yv9r0roGGsettingdirectors_provided,executives_providedandowners_providedasTrue
However, I can see that the response of the request req_XoNw3Yv9r0roGG contains the following
{
"capabilities": {
"card_issuing": "pending",
"transfers": "active",
},
"...",
"requirements": {
"alternatives": [],
"current_deadline": null,
"currently_due": [],
"disabled_reason": null,
"errors": [],
"eventually_due": [],
"past_due": [],
"pending_verification": [
"company.verification.document",
"person_1TGiMF5UQIDCNGrMW4BFCTQl.verification.additional_document",
"person_1TGiMF5UQIDCNGrMW4BFCTQl.verification.document",
],
},
}
And evt_1TGiMX5UQIDCNGrMLG5UC7b2 set the card_issuing capability to active
{
"object": {
"id": "card_issuing",
"object": "capability",
"account": "acct_1TGiM75UQIDCNGrM",
"future_requirements": {
"alternatives": [],
"current_deadline": null,
"currently_due": [],
"disabled_reason": null,
"errors": [],
"eventually_due": [],
"past_due": [],
"pending_verification": []
},
"requested": true,
"requested_at": 1774886883,
"requirements": {
"alternatives": [],
"current_deadline": null,
"currently_due": [],
"disabled_reason": null,
"errors": [],
"eventually_due": [],
"past_due": [],
"pending_verification": []
},
"status": "active"
},
"previous_attributes": {
"requirements": {
"disabled_reason": "requirements.fields_needed",
"pending_verification": [
"company.verification.document",
"person_1TGiMF5UQIDCNGrMW4BFCTQl.verification.additional_document",
"person_1TGiMF5UQIDCNGrMW4BFCTQl.verification.document"
]
},
"status": "pending"
}
}
Seems to be a different scenario
You never passed file_identity_document_success in account creation
I just need to see an example of this working how you said previously to compare
We initially never gave file_identity_document_success to the company.verification.document.front. I added it after It failed.
For example acct_1TGvsa4Rtfz6Cb1u was created without it and failed
{
"business_profile": {
"annual_revenue": {
"amount": "500000",
"currency": "EUR",
"fiscal_year_end": "2025-12-31"
},
"estimated_worker_count": "7274",
"mcc": "5598",
"name": "BE Company CoA",
"product_description": "Lorem ipsum dolor sit amet, consectetur adipiscing elit.",
"support_phone": "0000000000"
},
"business_type": "company",
"capabilities": {
"card_issuing": {
"requested": "True"
},
"transfers": {
"requested": "True"
}
},
"company": {
"address": {
"city": "City",
"country": "BE",
"line1": "address_full_match",
"postal_code": "2660",
"state": "State"
},
"name": "BE Company CoA",
"phone": "0000000000",
"tax_id": "*********"
},
"controller": {
"fees": {
"payer": "application"
},
"losses": {
"payments": "application"
},
"requirement_collection": "application",
"stripe_dashboard": {
"type": "none"
}
},
"country": "BE",
"email": "demo@example.com",
"external_account": "btok_be",
"settings": {
"card_issuing": {
"tos_acceptance": {
"date": "1774938861",
"ip": "127.0.0.1"
}
},
"payouts": {
"debit_negative_balances": "True"
}
},
"tos_acceptance": {
"date": "1774938861",
"ip": "127.0.0.1"
}
}
And it's capability.updated event evt_1TGvsy4Rtfz6Cb1uKKd6xjLp:
{
"object": {
"id": "card_issuing",
"object": "capability",
"account": "acct_1TGvsa4Rtfz6Cb1u",
"future_requirements": {
"alternatives": [],
"current_deadline": null,
"currently_due": [],
"disabled_reason": null,
"errors": [],
"eventually_due": [],
"past_due": [],
"pending_verification": []
},
"requested": true,
"requested_at": 1774938867,
"requirements": {
"alternatives": [],
"current_deadline": null,
"currently_due": [],
"disabled_reason": "requirements.fields_needed",
"errors": [],
"eventually_due": [],
"past_due": [],
"pending_verification": [
"company.verification.document"
]
},
"status": "pending"
},
"previous_attributes": {
"requirements": {
"pending_verification": [
"company.verification.document",
"person_1TGvsh4Rtfz6Cb1udMSZJeTp.verification.additional_document",
"person_1TGvsh4Rtfz6Cb1udMSZJeTp.verification.document"
]
}
}
}
Sorry I think I'm confused then. What worked previously that is not working now?
Previously when creating the test account, we did not provide any company.verification.document.
So we would:
- Create the account with test information
- Create a representative
- Set the representative as the director, executive, owner
And the card_issuing capability would be set as active by the end.
However now,
When creating the account the same way or when providing file_identity_document_success as company.verification.document.front,
the account has the card_issuing capability remaining in pending with the company.verification.document requirement still being there.
FYI i'm taking over for my colleague, gimme just a few minutes to catch up
ok i think i've got a handle on the question, lemme do some digging, i'll let you know if i have any questions
sorry for the delay, this is a tricky one. real quick, can you confirm if you're still running into this?