Class PaymentIntentConfirmParams.PaymentMethodOptions.Konbini

Enclosing class:

public static class PaymentIntentConfirmParams.PaymentMethodOptions.Konbini extends Object
  • Method Details

    • builder

    • getConfirmationNumber

      public Object getConfirmationNumber()
      An optional 10 to 11 digit numeric-only string determining the confirmation code at applicable convenience stores. Must not consist of only zeroes and could be rejected in case of insufficient uniqueness. We recommend to use the customer's phone number.
    • getExpiresAfterDays

      public Object getExpiresAfterDays()
      The number of calendar days (between 1 and 60) after which Konbini payment instructions will expire. For example, if a PaymentIntent is confirmed with Konbini and expires_after_days set to 2 on Monday JST, the instructions will expire on Wednesday 23:59:59 JST. Defaults to 3 days.
    • getExpiresAt

      public Object getExpiresAt()
      The timestamp at which the Konbini payment instructions will expire. Only one of expires_after_days or expires_at may be set.
    • getExtraParams

      public Map<String,Object> getExtraParams()
      Map of extra parameters for custom features not available in this client library. The content in this map is not serialized under this field's @SerializedName value. Instead, each key/value pair is serialized as if the key is a root-level field (serialized) name in this param object. Effectively, this map is flattened to its parent instance.
    • getProductDescription

      public Object getProductDescription()
      A product descriptor of up to 22 characters, which will appear to customers at the convenience store.
    • getSetupFutureUsage

      Indicates that you intend to make future payments with this PaymentIntent's payment method.

      Providing this parameter will attach the payment method to the PaymentIntent's Customer, if present, after the PaymentIntent is confirmed and any required actions from the user are complete. If no Customer was provided, the payment method can still be attached to a Customer after the transaction completes.

      When processing card payments, Stripe also uses setup_future_usage to dynamically optimize your payment flow and comply with regional legislation and network rules, such as SCA.

      If setup_future_usage is already set and you are performing a request using a publishable key, you may only update the value from on_session to off_session.