Package com.stripe.model

Class Capability.Requirements

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

  • Constructor Details

    • Requirements

      public Requirements()

  • Method Details

    • getAlternatives

      public List<Capability.Requirements.Alternative> getAlternatives()
      Fields that are due and can be resolved by providing the corresponding alternative fields instead. Multiple alternatives can reference the same original_fields_due. When this happens, any of these alternatives can serve as a pathway for attempting to resolve the fields. Additionally, providing original_fields_due again also serves as a pathway for attempting to resolve the fields.

    • getCurrentDeadline

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

    • getCurrentlyDue

      public List<String> getCurrentlyDue()
      Fields that need to be resolved to keep the capability enabled. If not resolved by current_deadline, these fields will appear in past_due as well, and the capability is disabled.

    • getDisabledReason

      public String getDisabledReason()
      Description of why the capability is disabled. Learn more about handling verification issues.

      One of other, paused.inactivity, pending.onboarding, pending.review, platform_disabled, platform_paused, rejected.inactivity, rejected.other, rejected.unsupported_business, or requirements.fields_needed.

    • getErrors

      public List<Capability.Requirements.Errors> 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, and current_deadline becomes set.

    • getPastDue

      public List<String> getPastDue()
      Fields that haven't been resolved by current_deadline. These fields need to be resolved to enable the capability on the account.

    • 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<Capability.Requirements.Alternative> alternatives)
      Fields that are due and can be resolved by providing the corresponding alternative fields instead. Multiple alternatives can reference the same original_fields_due. When this happens, any of these alternatives can serve as a pathway for attempting to resolve the fields. Additionally, providing original_fields_due again also serves as a pathway for attempting to resolve the fields.

    • setCurrentDeadline

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

    • setCurrentlyDue

      public void setCurrentlyDue(List<String> currentlyDue)
      Fields that need to be resolved to keep the capability enabled. If not resolved by current_deadline, these fields will appear in past_due as well, and the capability is disabled.

    • setDisabledReason

      public void setDisabledReason(String disabledReason)
      Description of why the capability is disabled. Learn more about handling verification issues.

      One of other, paused.inactivity, pending.onboarding, pending.review, platform_disabled, platform_paused, rejected.inactivity, rejected.other, rejected.unsupported_business, or requirements.fields_needed.

    • setErrors

      public void setErrors(List<Capability.Requirements.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, and current_deadline becomes set.

    • setPastDue

      public void setPastDue(List<String> pastDue)
      Fields that haven't been resolved by current_deadline. These fields need to be resolved to enable the capability on the account.

    • 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