bachir_api

[tribal pawn]

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

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

[plush lichen]

{
  "object": "list",
  "data": [
    {
      "id": "ba_1OJ4alQjkgN4fKlRjnqqd0TQ",
      "object": "bank_account",
      "account": "acct_1NDAdEQjkgN4fKlR",
      "account_holder_name": null,
      "account_holder_type": null,
      "account_type": null,
      "available_payout_methods": [
        "standard"
      ],
      "bank_name": "GREEN DOT BANK",
      "country": "US",
      "currency": "usd",
      "default_for_currency": true,
      "financial_account": null,
      "fingerprint": "bPOsSldJWWUZ7IQ1",
      "future_requirements": {
        "currently_due": [],
        "errors": [],
        "past_due": [],
        "pending_verification": []
      },
      "last4": "6586",
      "metadata": {},
      "requirements": {
        "currently_due": [],
        "errors": [],
        "past_due": [],
        "pending_verification": []
      },
      "routing_number": "124303214",
      "status": "new"
    }
  ],
  "has_more": false,
  "url": "/v1/accounts/acct_1NDAdEQjkgN4fKlR/external_accounts"
}

[left girder]

https://docs.stripe.com/api/external_account_bank_accounts/object
The external account object isn't expected to have a created property, according to the API reference

So i would not expect this for any API calls, whether using the Stripe CLI or not.

I can't speak to what the Dashboard shows for these, it's possible it aggregates other information into the view that's not available via API

What are you trying to do, exactly?

[plush lichen]

We want to be able to track external account updates on connected accounts in order to do fraud investigations (like account take overs etc...), so we need to catchup this data into our data pipeline, and the date of creation of external accounts is needed for it.

Is there another way we can get this info ?

[left girder]

Gotcha

I would say the best way to learn about new/updated external accounts promptly is via webhooks.
The account.external_account.created event in particular for new external accounts: https://docs.stripe.com/api/events/types#event_types-account.external_account.created

There are corresponding .updated and .deleted events, too

If you wanted to record the creation date for later reference, you could add that to the external account metadata

[plush lichen]

Indeed we are listenning to these webhooks, but they aren't helpful for catching up historical data

Is there any reason the API doesn't have this information ? Is it for security reasons ? It seems such a natural data to have.

[left girder]

It does seem a bit unexpected, since most of our objects have created dates. I'll report that feedback/request nd hopefully we can add it in future.

[plush lichen]

Alright great, I'll try to find another way or wait for the update. Thanks for your help ✌️

[hearty nova]

Not immediately sure why this timestamp isn't available here, I think we have it for other objects, so I don't think we have any inherent issues with exposing this kind of info. I can file feedback about exposing this timestamp.

[plush lichen]

Thanks - do you know how long this usually takes ? Just to know if I can tell my fraud team to wait or to find another way

[hearty nova]

I would say find another way, unfortunately I can't guarantee if/when we can add this