Class Account.FutureRequirements

java.lang.Object
com.stripe.model.StripeObject
com.stripe.model.Account.FutureRequirements
All Implemented Interfaces:
StripeObjectInterface
Enclosing class:
Account

public static class Account.FutureRequirements extends StripeObject
For more details about FutureRequirements, please refer to the API Reference.
  • Constructor Details

    • FutureRequirements

      public FutureRequirements()
  • Method Details

    • getAlternatives

      public List<Account.FutureRequirements.Alternative> getAlternatives()
      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.
    • getCurrentDeadline

      public Long getCurrentDeadline()
      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.
    • getCurrentlyDue

      public List<String> getCurrentlyDue()
      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.
    • getDisabledReason

      public String getDisabledReason()
      This is typed as an enum for consistency with requirements.disabled_reason.

      One of action_required.requested_capabilities, listed, other, platform_paused, rejected.fraud, rejected.incomplete_verification, rejected.listed, rejected.other, rejected.platform_fraud, rejected.platform_other, rejected.platform_terms_of_service, rejected.terms_of_service, requirements.past_due, requirements.pending_verification, or under_review.

    • getErrors

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

      public List<String> getEventuallyDue()
      Fields you must collect when all thresholds are reached. As they become required, they appear in currently_due as well.
    • getPastDue

      public List<String> getPastDue()
      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.
    • getPendingVerification

      public List<String> getPendingVerification()
      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.
    • setAlternatives

      public void setAlternatives(List<Account.FutureRequirements.Alternative> alternatives)
      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.
    • setCurrentDeadline

      public void setCurrentDeadline(Long currentDeadline)
      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.
    • setCurrentlyDue

      public void setCurrentlyDue(List<String> currentlyDue)
      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.
    • setDisabledReason

      public void setDisabledReason(String disabledReason)
      This is typed as an enum for consistency with requirements.disabled_reason.

      One of action_required.requested_capabilities, listed, other, platform_paused, rejected.fraud, rejected.incomplete_verification, rejected.listed, rejected.other, rejected.platform_fraud, rejected.platform_other, rejected.platform_terms_of_service, rejected.terms_of_service, requirements.past_due, requirements.pending_verification, or under_review.

    • setErrors

      public void setErrors(List<Account.FutureRequirements.Errors> errors)
      Details about validation and verification failures for due requirements that must be resolved.
    • setEventuallyDue

      public void setEventuallyDue(List<String> eventuallyDue)
      Fields you must collect when all thresholds are reached. As they become required, they appear in currently_due as well.
    • setPastDue

      public void setPastDue(List<String> pastDue)
      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.
    • setPendingVerification

      public void setPendingVerification(List<String> pendingVerification)
      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.
    • equals

      public boolean equals(Object o)
      Overrides:
      equals in class Object
    • canEqual

      protected boolean canEqual(Object other)
    • hashCode

      public int hashCode()
      Overrides:
      hashCode in class Object