Struct AccountRequirements 

pub struct AccountRequirements {
    pub alternatives: Option<Vec<AccountRequirementsAlternative>>,
    pub current_deadline: Option<Timestamp>,
    pub currently_due: Option<Vec<String>>,
    pub disabled_reason: Option<AccountRequirementsDisabledReason>,
    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 by which the fields in currently_due must be collected to keep the account enabled. These fields may disable the account sooner if the next threshold is reached before they are collected.

currently_due: Option<Vec<String>>

Fields that need to be resolved to keep the account enabled. If not resolved by current_deadline, these fields will appear in past_due as well, and the account is disabled.

disabled_reason: Option<AccountRequirementsDisabledReason>

If the account is disabled, this enum describes why. Learn more about handling verification issues.

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, and current_deadline becomes set.

past_due: Option<Vec<String>>

Fields that haven’t been resolved by current_deadline. These fields need to be resolved to enable the account.

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 AccountRequirements

fn clone(&self) -> AccountRequirements

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for AccountRequirements

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

Formats the value using the given formatter.

impl Deserialize for AccountRequirements

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

The only correct implementation of this method is:

impl FromValueOpt for AccountRequirements

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

impl ObjectDeser for AccountRequirements

type Builder = AccountRequirementsBuilder