Class: Stripe::SetupIntentService::UpdateParams::PaymentMethodOptions::Card

Inherits:
RequestParams
  • Object
show all
Defined in:
lib/stripe/services/setup_intent_service.rb

Defined Under Namespace

Classes: MandateOptions, ThreeDSecure

Instance Attribute Summary collapse

Instance Method Summary collapse

Methods inherited from RequestParams

#to_h

Constructor Details

#initialize(mandate_options: nil, moto: nil, network: nil, request_three_d_secure: nil, three_d_secure: nil) ⇒ Card

Returns a new instance of Card.



1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
 
# File 'lib/stripe/services/setup_intent_service.rb', line 1816

def initialize(
  mandate_options: nil,
  moto: nil,
  network: nil,
  request_three_d_secure: nil,
  three_d_secure: nil
)
  @mandate_options = mandate_options
  @moto = moto
  @network = network
  @request_three_d_secure = request_three_d_secure
  @three_d_secure = three_d_secure
end

Instance Attribute Details

#mandate_options ⇒ Object

Configuration options for setting up an eMandate for cards issued in India.



1803
1804
1805
 
# File 'lib/stripe/services/setup_intent_service.rb', line 1803

def mandate_options
  @mandate_options
end

#moto ⇒ Object

When specified, this parameter signals that a card has been collected as MOTO (Mail Order Telephone Order) and thus out of scope for SCA. This parameter can only be provided during confirmation.



1807
1808
1809
 
# File 'lib/stripe/services/setup_intent_service.rb', line 1807

def moto
  @moto
end

#network ⇒ Object

Selected network to process this SetupIntent on. Depends on the available networks of the card attached to the SetupIntent. Can be only set confirm-time.



1809
1810
1811
 
# File 'lib/stripe/services/setup_intent_service.rb', line 1809

def network
  @network
end

#request_three_d_secure ⇒ Object

We strongly recommend that you rely on our SCA Engine to automatically prompt your customers for authentication based on risk level and [other requirements](stripe.com/docs/strong-customer-authentication). 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](stripe.com/docs/payments/3d-secure/authentication-flow#manual-three-ds) for more information on how this configuration interacts with Radar and our SCA Engine.



1811
1812
1813
 
# File 'lib/stripe/services/setup_intent_service.rb', line 1811

def request_three_d_secure
  @request_three_d_secure
end

#three_d_secure ⇒ Object

If 3D Secure authentication was performed with a third-party provider, the authentication details to use for this setup.



1814
1815
1816
 
# File 'lib/stripe/services/setup_intent_service.rb', line 1814

def three_d_secure
  @three_d_secure
end