StripeAPI.Types.PersonFutureRequirements

Constructors

• PersonFutureRequirements
  • personFutureRequirementsAlternatives :: Maybe (Nullable [AccountRequirementsAlternative])

    alternatives: Fields that are due and can be satisfied by providing the corresponding alternative fields instead.

  • personFutureRequirementsCurrentlyDue :: [Text]

    currently_due: Fields that need to be collected to keep the person's account enabled. If not collected by the account's `future_requirements[current_deadline]`, these fields will transition to the main `requirements` hash, and may immediately become `past_due`, but the account may also be given a grace period depending on the account's enablement state prior to transition.

  • personFutureRequirementsErrors :: [AccountRequirementsError]

    errors: Fields that are `currently_due` and need to be collected again because validation or verification failed.

  • personFutureRequirementsEventuallyDue :: [Text]

    eventually_due: Fields that need to be collected assuming all volume thresholds are reached. As they become required, they appear in `currently_due` as well, and the account's `future_requirements[current_deadline]` becomes set.

  • personFutureRequirementsPastDue :: [Text]

    past_due: Fields that weren't collected by the account's `requirements.current_deadline`. These fields need to be collected to enable the person's account. New fields will never appear here; `future_requirements.past_due` will always be a subset of `requirements.past_due`.

  • personFutureRequirementsPendingVerification :: [Text]

    pending_verification: Fields that may become required depending on the results of verification or review. Will be an empty array unless an asynchronous verification is pending. If verification fails, these fields move to `eventually_due` or `currently_due`.