Package com.stripe.param.checkout

Class SessionCreateParams.PaymentMethodOptions.Card.Builder

java.lang.Object
com.stripe.param.checkout.SessionCreateParams.PaymentMethodOptions.Card.Builder
Enclosing class:
SessionCreateParams.PaymentMethodOptions.Card
public static class SessionCreateParams.PaymentMethodOptions.Card.Builder extends Object

  • Constructor Details

    • Builder

      public Builder()

  • Method Details

    • build

      public SessionCreateParams.PaymentMethodOptions.Card build()
      Finalize and obtain parameter instance from this builder.

    • putExtraParam

      public SessionCreateParams.PaymentMethodOptions.Card.Builder putExtraParam(String key, Object value)
      Add a key/value pair to `extraParams` map. A map is initialized for the first `put/putAll` call, and subsequent calls add additional key/value pairs to the original map. See SessionCreateParams.PaymentMethodOptions.Card.extraParams for the field documentation.

    • putAllExtraParam

      public SessionCreateParams.PaymentMethodOptions.Card.Builder putAllExtraParam(Map<String,Object> map)
      Add all map key/value pairs to `extraParams` map. A map is initialized for the first `put/putAll` call, and subsequent calls add additional key/value pairs to the original map. See SessionCreateParams.PaymentMethodOptions.Card.extraParams for the field documentation.

    • setInstallments

      public SessionCreateParams.PaymentMethodOptions.Card.Builder setInstallments(SessionCreateParams.PaymentMethodOptions.Card.Installments installments)
      Installment options for card payments.

    • setRequestThreeDSecure

      public SessionCreateParams.PaymentMethodOptions.Card.Builder setRequestThreeDSecure(SessionCreateParams.PaymentMethodOptions.Card.RequestThreeDSecure requestThreeDSecure)
      We strongly recommend that you rely on our SCA Engine to automatically prompt your customers for authentication based on risk level and other requirements. However, if you wish to request 3D Secure based on logic from your own fraud engine, provide this option. If not provided, this value defaults to automatic. Read our guide on manually requesting 3D Secure for more information on how this configuration interacts with Radar and our SCA Engine.

    • setSetupFutureUsage

      public SessionCreateParams.PaymentMethodOptions.Card.Builder setSetupFutureUsage(SessionCreateParams.PaymentMethodOptions.Card.SetupFutureUsage setupFutureUsage)
      Indicates that you intend to make future payments with this PaymentIntent's payment method.

      If you provide a Customer with the PaymentIntent, you can use this parameter to attach the payment method to the Customer after the PaymentIntent is confirmed and the customer completes any required actions. If you don't provide a Customer, you can still attach the payment method to a Customer after the transaction completes.

      If the payment method is card_present and isn't a digital wallet, Stripe creates and attaches a generated_card payment method representing the card to the Customer instead.

      When processing card payments, Stripe uses setup_future_usage to help you comply with regional legislation and network rules, such as SCA.

    • setStatementDescriptorSuffixKana

      public SessionCreateParams.PaymentMethodOptions.Card.Builder setStatementDescriptorSuffixKana(String statementDescriptorSuffixKana)
      Provides information about a card payment that customers see on their statements. Concatenated with the Kana prefix (shortened Kana descriptor) or Kana statement descriptor that’s set on the account to form the complete statement descriptor. Maximum 22 characters. On card statements, the concatenation of both prefix and suffix (including separators) will appear truncated to 22 characters.

    • setStatementDescriptorSuffixKanji

      public SessionCreateParams.PaymentMethodOptions.Card.Builder setStatementDescriptorSuffixKanji(String statementDescriptorSuffixKanji)
      Provides information about a card payment that customers see on their statements. Concatenated with the Kanji prefix (shortened Kanji descriptor) or Kanji statement descriptor that’s set on the account to form the complete statement descriptor. Maximum 17 characters. On card statements, the concatenation of both prefix and suffix (including separators) will appear truncated to 17 characters.