Struct AccountCapabilityRequirements 

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

Fields

alternatives: Option<Vec<AccountRequirementsAlternative>>

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

current_deadline: Option<Timestamp>

The date by which all required account information must be both submitted and verified. This includes fields listed in currently_due as well as those in pending_verification. If any required information is missing or unverified by this date, the account may be disabled. Note that current_deadline may change if additional currently_due requirements are requested.

currently_due: Vec<String>

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

disabled_reason: Option<AccountCapabilityRequirementsDisabledReason>

Description of why the capability is disabled. Learn more about handling verification issues.

errors: Vec<AccountRequirementsError>

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

eventually_due: 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: Vec<String>

Fields that weren’t collected by current_deadline. These fields need to be collected to enable the capability on the account.

pending_verification: Vec<String>

Fields that might become required depending on the results of verification or review. It’s an empty array unless an asynchronous verification is pending. If verification fails, these fields move to eventually_due, currently_due, or past_due. Fields might appear in eventually_due, currently_due, or past_due and in pending_verification if verification fails but another verification is still pending.

Trait Implementations

impl Clone for AccountCapabilityRequirements

fn clone(&self) -> AccountCapabilityRequirements

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for AccountCapabilityRequirements

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

Formats the value using the given formatter.

impl Deserialize for AccountCapabilityRequirements

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

The only correct implementation of this method is:

impl FromValueOpt for AccountCapabilityRequirements

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

impl ObjectDeser for AccountCapabilityRequirements

type Builder = AccountCapabilityRequirementsBuilder