# `Stripe.Resources.Invoice.PaymentSettings.PaymentMethodOptions.Card`
[🔗](https://github.com/jeffhuen/tiger_stripe/blob/main/lib/stripe/resources/invoice.ex#L602)

Nested struct within the parent resource.

# `t`

```elixir
@type t() :: %Stripe.Resources.Invoice.PaymentSettings.PaymentMethodOptions.Card{
  installments:
    Stripe.Resources.Invoice.PaymentSettings.PaymentMethodOptions.Card.Installments.t()
    | nil,
  request_three_d_secure: String.t() | nil
}
```

* `installments`
* `request_three_d_secure` - We strongly recommend that you rely on our SCA Engine to automatically prompt your customers for authentication based on risk level and [other requirements](https://docs.stripe.com/strong-customer-authentication). However, if you wish to request 3D Secure based on logic from your own fraud engine, provide this option. Read our guide on [manually requesting 3D Secure](https://docs.stripe.com/payments/3d-secure/authentication-flow#manual-three-ds) for more information on how this configuration interacts with Radar and our SCA Engine. Possible values: `any`, `automatic`, `challenge`. Nullable.

---

*Consult [api-reference.md](api-reference.md) for complete listing*