#spartanplaya

1 messages · Page 1 of 1 (latest)

keen shoreBOT
surreal grove
#

Can you tell me more about where you see that error and what your code is doing at that point? These requirements should be expected to show up in the future_requirements hash until the date specified by the current_deadline property https://docs.stripe.com/api/accounts/object#account_object-future_requirements-current_deadline

near wyvern
#

Yeah for sure!

      %{requirements: %{disabled_reason: disabled_reason}} when disabled_reason in @rejected_reasons ->
        ProcessorAccount.rejected()

      %{requirements: %{currently_due: [], eventually_due: [], disabled_reason: _disabled_reason}} ->
        ProcessorAccount.under_review()

      %{requirements: %{current_deadline: deadline}} when is_integer(deadline) ->
        current_time = :os.system_time(:seconds)
        restricted_status(deadline, current_time)

      %{requirements: %{currently_due: [], eventually_due: [_ | _]}} ->
        ProcessorAccount.approved()

      %{requirements: %{currently_due: [], eventually_due: [], disabled_reason: nil}} ->
        ProcessorAccount.approved()

      _ ->
        ProcessorAccount.information_required()

This is the elixir code we are running to try to map the account object -> statuses to show our users (mostly to prompt them to please update their stripe account by the specified date).

What I think I'm hearing is that we should NOT be checking requirements for the upcoming verification requirements, but instead future_requirements? My concern then would be that we may notify users of a change that the stripe connect flow would not support them fixing quite yet.

#

Also, to TLDR the elixir code, we are just using pattern matching to be like 'if there is a current_deadline in requirements and it's an integer, set it to restricted_soon

surreal grove