View Source ExOAPI.Stripe.Schemas.AccountCapabilityFutureRequirements (exoapi_stripe v0.1.4)
::alternatives :: ExOAPI.Stripe.Schemas.AccountRequirementsAlternative
:current_deadline :: :integer
Date on which future_requirements
merges with the main requirements
hash and future_requirements
becomes empty. After the transition, currently_due
requirements may immediately become past_due
, but the account may also be given a grace period depending on the capability's enablement state prior to transitioning.
::currently_due :: :string
:disabled_reason :: :string
This is typed as a string for consistency with requirements.disabled_reason
, but it safe to assume future_requirements.disabled_reason
is empty because fields in future_requirements
will never disable the account.
::errors :: ExOAPI.Stripe.Schemas.AccountRequirementsError
::eventually_due :: :string
::past_due :: :string
::pending_verification :: :string
Link to this section Summary
Link to this section Types
@type params() :: map()
@type t() :: %ExOAPI.Stripe.Schemas.AccountCapabilityFutureRequirements{ alternatives: [ExOAPI.Stripe.Schemas.AccountRequirementsAlternative.t()], current_deadline: integer() | nil, currently_due: [String.t()] | nil, disabled_reason: String.t() | nil, errors: [ExOAPI.Stripe.Schemas.AccountRequirementsError.t()], eventually_due: [String.t()] | nil, past_due: [String.t()] | nil, pending_verification: [String.t()] | nil }
Link to this section Functions
@spec changeset(t(), params()) :: Ecto.Changeset.t()