Package com.stripe.model

Class Person.FutureRequirements

java.lang.Object
com.stripe.model.StripeObject
com.stripe.model.Person.FutureRequirements
All Implemented Interfaces:
StripeObjectInterface
Enclosing class:
Person
public static class Person.FutureRequirements extends StripeObject
For more details about FutureRequirements, please refer to the API Reference.

  • Constructor Details

    • FutureRequirements

      public FutureRequirements()

  • Method Details

    • getAlternatives

      public List<Person.FutureRequirements.Alternative> getAlternatives()
      Fields that are due and can be satisfied by providing the corresponding alternative fields instead.

    • getCurrentlyDue

      public List<String> getCurrentlyDue()
      Fields that need to be collected to keep the person's account enabled. If not collected by the account's future_requirements[current_deadline], these fields will transition to the main requirements hash, and may immediately become past_due, but the account may also be given a grace period depending on the account's enablement state prior to transition.

    • getErrors

      public List<Person.FutureRequirements.Errors> getErrors()
      Fields that are currently_due and need to be collected again because validation or verification failed.

    • 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, and the account's future_requirements[current_deadline] becomes set.

    • getPastDue

      public List<String> getPastDue()
      Fields that weren't collected by the account's requirements.current_deadline. These fields need to be collected to enable the person's account. New fields will never appear here; future_requirements.past_due will always be a subset of requirements.past_due.

    • getPendingVerification

      public List<String> getPendingVerification()
      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 or currently_due. Fields might appear in eventually_due or currently_due and in pending_verification if verification fails but another verification is still pending.

    • setAlternatives

      public void setAlternatives(List<Person.FutureRequirements.Alternative> alternatives)
      Fields that are due and can be satisfied by providing the corresponding alternative fields instead.

    • setCurrentlyDue

      public void setCurrentlyDue(List<String> currentlyDue)
      Fields that need to be collected to keep the person's account enabled. If not collected by the account's future_requirements[current_deadline], these fields will transition to the main requirements hash, and may immediately become past_due, but the account may also be given a grace period depending on the account's enablement state prior to transition.

    • setErrors

      public void setErrors(List<Person.FutureRequirements.Errors> errors)
      Fields that are currently_due and need to be collected again because validation or verification failed.

    • 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, and the account's future_requirements[current_deadline] becomes set.

    • setPastDue

      public void setPastDue(List<String> pastDue)
      Fields that weren't collected by the account's requirements.current_deadline. These fields need to be collected to enable the person's account. New fields will never appear here; future_requirements.past_due will always be a subset of requirements.past_due.

    • setPendingVerification

      public void setPendingVerification(List<String> pendingVerification)
      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 or currently_due. Fields might appear in eventually_due or currently_due and in pending_verification if verification fails but another verification 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