# `Stripe.Resources.BankAccount.FutureRequirements`
[🔗](https://github.com/jeffhuen/tiger_stripe/blob/main/lib/stripe/resources/bank_account.ex#L87)

Nested struct within the parent resource.

# `t`

```elixir
@type t() :: %Stripe.Resources.BankAccount.FutureRequirements{
  currently_due: [String.t()] | nil,
  errors: [Stripe.Resources.BankAccount.FutureRequirements.Errors.t()] | nil,
  past_due: [String.t()] | nil,
  pending_verification: [String.t()] | nil
}
```

* `currently_due` - Fields that need to be resolved to keep the external account enabled. If not resolved by `current_deadline`, these fields will appear in `past_due` as well, and the account is disabled. Nullable.
* `errors` - Details about validation and verification failures for `due` requirements that must be resolved. Nullable.
* `past_due` - Fields that haven't been resolved by `current_deadline`. These fields need to be resolved to enable the external account. Nullable.
* `pending_verification` - Fields that are being reviewed, or might become required depending on the results of a review. If the review fails, these fields can move to `eventually_due`, `currently_due`, `past_due` or `alternatives`. Fields might appear in `eventually_due`, `currently_due`, `past_due` or `alternatives` and in `pending_verification` if one verification fails but another is still pending. Nullable.

---

*Consult [api-reference.md](api-reference.md) for complete listing*