Class PaymentIntent.PaymentMethodOptions.Card
- All Implemented Interfaces:
StripeObjectInterface
- Enclosing class:
- PaymentIntent.PaymentMethodOptions
-
Nested Class Summary
Modifier and TypeClassDescriptionstatic class
static class
Type of installment plan, one offixed_count
. -
Field Summary
Fields inherited from class com.stripe.model.StripeObject
PRETTY_PRINT_GSON
-
Constructor Summary
-
Method Summary
Modifier and TypeMethodDescriptionprotected boolean
boolean
Controls when the funds will be captured from the customer's account.Installment details for this payment (Mexico only).Configuration options for setting up an eMandate for cards issued in India.Selected network to process this payment intent on.Request ability to capture beyond the standard authorization validity window for this PaymentIntent.Request ability to increment the authorization for this PaymentIntent.Request ability to make multiple captures for this PaymentIntent.Request ability to overcapture for this PaymentIntent.We strongly recommend that you rely on our SCA Engine to automatically prompt your customers for authentication based on risk level and other requirements.When enabled, using a card that is attached to a customer will require the CVC to be provided again (i.e.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
setCaptureMethod
(String captureMethod) Controls when the funds will be captured from the customer's account.void
Installment details for this payment (Mexico only).void
Configuration options for setting up an eMandate for cards issued in India.void
setNetwork
(String network) Selected network to process this payment intent on.void
setRequestExtendedAuthorization
(String requestExtendedAuthorization) Request ability to capture beyond the standard authorization validity window for this PaymentIntent.void
setRequestIncrementalAuthorization
(String requestIncrementalAuthorization) Request ability to increment the authorization for this PaymentIntent.void
setRequestMulticapture
(String requestMulticapture) Request ability to make multiple captures for this PaymentIntent.void
setRequestOvercapture
(String requestOvercapture) Request ability to overcapture for this PaymentIntent.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
setRequireCvcRecollection
(Boolean requireCvcRecollection) When enabled, using a card that is attached to a customer will require the CVC to be provided again (i.e.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, equals, getLastResponse, getRawJsonObject, setLastResponse, toJson, toString
-
Constructor Details
-
Card
public Card()
-
-
Method Details
-
getCaptureMethod
Controls when the funds will be captured from the customer's account.Equal to
manual
. -
getInstallments
Installment details for this payment (Mexico only).For more information, see the installments integration guide.
-
getMandateOptions
Configuration options for setting up an eMandate for cards issued in India. -
getNetwork
Selected network to process this payment intent on. Depends on the available networks of the card attached to the payment intent. Can be only set confirm-time. -
getRequestExtendedAuthorization
Request ability to capture beyond the standard authorization validity window for this PaymentIntent.One of
if_available
, ornever
. -
getRequestIncrementalAuthorization
Request ability to increment the authorization for this PaymentIntent.One of
if_available
, ornever
. -
getRequestMulticapture
Request ability to make multiple captures for this PaymentIntent.One of
if_available
, ornever
. -
getRequestOvercapture
Request ability to overcapture for this PaymentIntent.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
. -
getRequireCvcRecollection
When enabled, using a card that is attached to a customer will require the CVC to be provided again (i.e. using the cvc_token parameter). -
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. -
setCaptureMethod
Controls when the funds will be captured from the customer's account.Equal to
manual
. -
setInstallments
Installment details for this payment (Mexico only).For more information, see the installments integration guide.
-
setMandateOptions
public void setMandateOptions(PaymentIntent.PaymentMethodOptions.Card.MandateOptions mandateOptions) Configuration options for setting up an eMandate for cards issued in India. -
setNetwork
Selected network to process this payment intent on. Depends on the available networks of the card attached to the payment intent. Can be only set confirm-time. -
setRequestExtendedAuthorization
Request ability to capture beyond the standard authorization validity window for this PaymentIntent.One of
if_available
, ornever
. -
setRequestIncrementalAuthorization
Request ability to increment the authorization for this PaymentIntent.One of
if_available
, ornever
. -
setRequestMulticapture
Request ability to make multiple captures for this PaymentIntent.One of
if_available
, ornever
. -
setRequestOvercapture
Request ability to overcapture for this PaymentIntent.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
. -
setRequireCvcRecollection
When enabled, using a card that is attached to a customer will require the CVC to be provided again (i.e. using the cvc_token parameter). -
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()
-