Struct AccountFutureRequirements 

pub struct AccountFutureRequirements {
    pub alternatives: Option<Vec<AccountRequirementsAlternative>>,
    pub current_deadline: Option<Timestamp>,
    pub currently_due: Option<Vec<String>>,
    pub disabled_reason: Option<AccountFutureRequirementsDisabledReason>,
    pub errors: Option<Vec<AccountRequirementsError>>,
    pub eventually_due: Option<Vec<String>>,
    pub past_due: Option<Vec<String>>,
    pub pending_verification: Option<Vec<String>>,
}

Fields

alternatives: Option<Vec<AccountRequirementsAlternative>>

Fields that are due and can be resolved by providing the corresponding alternative fields instead. Many alternatives can list the same original_fields_due, and any of these alternatives can serve as a pathway for attempting to resolve the fields again. Re-providing original_fields_due also serves as a pathway for attempting to resolve the fields again.

current_deadline: Option<Timestamp>

Date on which future_requirements becomes 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 its enablement state prior to transitioning.

currently_due: Option<Vec<String>>

Fields that need to be resolved to keep the account enabled. If not resolved by future_requirements[current_deadline], these fields will transition to the main requirements hash.

disabled_reason: Option<AccountFutureRequirementsDisabledReason>

This is typed as an enum for consistency with requirements.disabled_reason.

errors: Option<Vec<AccountRequirementsError>>

Details about validation and verification failures for due requirements that must be resolved.

eventually_due: Option<Vec<String>>

Fields you must collect when all thresholds are reached. As they become required, they appear in currently_due as well.

past_due: Option<Vec<String>>

Fields that haven’t been resolved by requirements.current_deadline. These fields need to be resolved to enable the capability on the account. future_requirements.past_due is a subset of requirements.past_due.

pending_verification: Option<Vec<String>>

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.

Trait Implementations

impl Clone for AccountFutureRequirements

fn clone(&self) -> AccountFutureRequirements

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for AccountFutureRequirements

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Deserialize for AccountFutureRequirements

fn begin(out: &mut Option<Self>) -> &mut dyn Visitor

The only correct implementation of this method is:

impl FromValueOpt for AccountFutureRequirements

fn from_value(v: Value) -> Option<Self>

impl ObjectDeser for AccountFutureRequirements

type Builder = AccountFutureRequirementsBuilder