Class Session.PaymentMethodOptions.Card
- All Implemented Interfaces:
StripeObjectInterface
- Enclosing class:
- Session.PaymentMethodOptions
-
Nested Class Summary
Nested ClassesModifier and TypeClassDescriptionstatic class
For more details about Installments, please refer to the API Reference.static class
For more details about Restrictions, please refer to the API Reference. -
Field Summary
Fields inherited from class com.stripe.model.StripeObject
PRETTY_PRINT_GSON
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionprotected boolean
boolean
Request ability to capture beyond the standard authorization validity window for this CheckoutSession.Request ability to increment the authorization for this CheckoutSession.Request ability to make multiple captures for this CheckoutSession.Request ability to overcapture for this CheckoutSession.We strongly recommend that you rely on our SCA Engine to automatically prompt your customers for authentication based on risk level and other requirements.Indicates that you intend to make future payments with this PaymentIntent's payment method.Provides information about a card payment that customers see on their statements.Provides information about a card payment that customers see on their statements.int
hashCode()
void
void
setRequestExtendedAuthorization
(String requestExtendedAuthorization) Request ability to capture beyond the standard authorization validity window for this CheckoutSession.void
setRequestIncrementalAuthorization
(String requestIncrementalAuthorization) Request ability to increment the authorization for this CheckoutSession.void
setRequestMulticapture
(String requestMulticapture) Request ability to make multiple captures for this CheckoutSession.void
setRequestOvercapture
(String requestOvercapture) Request ability to overcapture for this CheckoutSession.void
setRequestThreeDSecure
(String 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.void
void
setSetupFutureUsage
(String setupFutureUsage) Indicates that you intend to make future payments with this PaymentIntent's payment method.void
setStatementDescriptorSuffixKana
(String statementDescriptorSuffixKana) Provides information about a card payment that customers see on their statements.void
setStatementDescriptorSuffixKanji
(String statementDescriptorSuffixKanji) Provides information about a card payment that customers see on their statements.Methods inherited from class com.stripe.model.StripeObject
deserializeStripeObject, deserializeStripeObject, deserializeStripeObject, deserializeStripeObject, equals, getLastResponse, getRawJsonObject, setLastResponse, toJson, toString
-
Constructor Details
-
Card
public Card()
-
-
Method Details
-
getInstallments
-
getRequestExtendedAuthorization
Request ability to capture beyond the standard authorization validity window for this CheckoutSession.One of
if_available
, ornever
. -
getRequestIncrementalAuthorization
Request ability to increment the authorization for this CheckoutSession.One of
if_available
, ornever
. -
getRequestMulticapture
Request ability to make multiple captures for this CheckoutSession.One of
if_available
, ornever
. -
getRequestOvercapture
Request ability to overcapture for this CheckoutSession.One of
if_available
, ornever
. -
getRequestThreeDSecure
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 toautomatic
. Read our guide on manually requesting 3D Secure for more information on how this configuration interacts with Radar and our SCA Engine.One of
any
,automatic
, orchallenge
. -
getRestrictions
-
getSetupFutureUsage
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.One of
none
,off_session
, oron_session
. -
getStatementDescriptorSuffixKana
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. -
getStatementDescriptorSuffixKanji
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. -
setInstallments
-
setRequestExtendedAuthorization
Request ability to capture beyond the standard authorization validity window for this CheckoutSession.One of
if_available
, ornever
. -
setRequestIncrementalAuthorization
Request ability to increment the authorization for this CheckoutSession.One of
if_available
, ornever
. -
setRequestMulticapture
Request ability to make multiple captures for this CheckoutSession.One of
if_available
, ornever
. -
setRequestOvercapture
Request ability to overcapture for this CheckoutSession.One of
if_available
, ornever
. -
setRequestThreeDSecure
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 toautomatic
. Read our guide on manually requesting 3D Secure for more information on how this configuration interacts with Radar and our SCA Engine.One of
any
,automatic
, orchallenge
. -
setRestrictions
-
setSetupFutureUsage
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.One of
none
,off_session
, oron_session
. -
setStatementDescriptorSuffixKana
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
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. -
equals
-
canEqual
-
hashCode
public int hashCode()
-