Package com.stripe.model

Class Capability.FutureRequirements

java.lang.Object
com.stripe.model.StripeObject
com.stripe.model.Capability.FutureRequirements
All Implemented Interfaces:
StripeObjectInterface
Enclosing class:
Capability
public static class Capability.FutureRequirements extends StripeObject

  • Constructor Details

    • FutureRequirements

      public FutureRequirements()

  • Method Details

    • getAlternatives

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

    • getCurrentDeadline

      public Long getCurrentDeadline()
      Date on which future_requirements merges with 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 the capability's enablement state prior to transitioning.

    • getCurrentlyDue

      public List<String> getCurrentlyDue()
      Fields that need to be collected to keep the capability enabled. If not collected 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, but it safe to assume future_requirements.disabled_reason is null because fields in future_requirements will never disable the account.

      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.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 that need to be collected assuming all volume thresholds are reached. As they become required, they appear in currently_due as well.

    • getPastDue

      public List<String> getPastDue()
      Fields that weren't collected by requirements.current_deadline. These fields need to be collected to enable the capability on the 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<Capability.FutureRequirements.Alternative> alternatives)
      Fields that are due and can be satisfied by providing the corresponding alternative fields instead.

    • setCurrentDeadline

      public void setCurrentDeadline(Long currentDeadline)
      Date on which future_requirements merges with 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 the capability's enablement state prior to transitioning.

    • setCurrentlyDue

      public void setCurrentlyDue(List<String> currentlyDue)
      Fields that need to be collected to keep the capability enabled. If not collected 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, but it safe to assume future_requirements.disabled_reason is null because fields in future_requirements will never disable the account.

      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.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 that need to be collected assuming all volume thresholds are reached. As they become required, they appear in currently_due as well.

    • setPastDue

      public void setPastDue(List<String> pastDue)
      Fields that weren't collected by requirements.current_deadline. These fields need to be collected to enable the capability on the 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