stripeapi-1.0.0.0: Stripe-Library
Safe HaskellNone
LanguageHaskell2010

StripeAPI.Types.PersonRequirements

Description

Contains the types generated from the schema PersonRequirements

Synopsis

Documentation

data PersonRequirements Source #

Defines the object schema located at components.schemas.person_requirements in the specification.

Constructors

PersonRequirements 

Fields

  • personRequirementsCurrentlyDue :: [Text]

    currently_due: Fields that need to be collected to keep the person's account enabled. If not collected by the account's `current_deadline`, these fields appear in `past_due` as well, and the account is disabled.

  • personRequirementsErrors :: [AccountRequirementsError]

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

  • personRequirementsEventuallyDue :: [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 `current_deadline` becomes set.

  • personRequirementsPastDue :: [Text]

    past_due: Fields that weren't collected by the account's `current_deadline`. These fields need to be collected to enable the person's account.

  • personRequirementsPendingVerification :: [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`, `currently_due`, or `past_due`.