Specify the layout for the Payment Element.
If you only pass a layout type ('accordion' or ‘tabs’)
without any additional parameters, t
he Payment Element renders using that layout and
the default values associated with it.
Control how mandates or other legal agreements are displayed in the Payment Element.
The default setting is auto, which causes legal agreements to only be shown when necessary.
By default, the Payment Element will display all the payment methods that the underlying Payment Intent was created with.
However, wallets like Apple Pay and Google Pay are not payment methods per the Payment Intent API. They will show when the Payment Intent has the card payment method and the customer is using a supported platform and have an active card in their account.
This is the auto behavior, and it is the default for choice for all wallets.
If you do not want to show a given wallet as a payment option, you can set its property in wallets to never.
A PaymentIntent guides you through the process of collecting a payment
from your customer.
We recommend that you create exactly one PaymentIntent for each order or
customer session in your system.
PaymentMethod objects represent your customer's payment instruments.
You can use them with PaymentIntents to collect payments or save them
to Customer objects to store instrument details for future payments.
Abstraction for details of a payment method.
In general this can be just the identifier of the payment method,
or be a class that contains more information depending on the payment type.
A SetupIntent guides you through the process of setting up and saving a
customer's payment credentials for future payments.
For example, you could use a SetupIntent to set up and save
your customer's card without immediately collecting a payment.
Later, you can use PaymentIntents to drive the payment flow.
Tokenization is the process Stripe uses to collect sensitive card or bank
account details, or personally identifiable information (PII), directly
from your customers in a secure manner. A token representing this
information is returned to your server to use. You should use our
recommended payments integrations to perform this process client-side. T
his ensures that no sensitive card data touches your server, and allows your
integration to operate in a PCI-compliant way.
By default, stripe.confirmPayment will always redirect to
your return_url after a successful confirmation.
If you set redirect: "if_required", then stripe.confirmPayment
will only redirect if your user chooses a redirect-based payment method.
Reason for cancellation of this PaymentIntent,
either user-provided (duplicate, fraudulent, requested_by_customer, or
abandoned) or generated by Stripe internally (failed_invoice, void_invoice,
or automatic).
The type of the PaymentMethod.
An additional hash is included on the PaymentMethod with a name matching
this value. It contains additional information specific to the PaymentMethod
type.
Reason for cancellation of this SetupIntent,
either user-provided (duplicate, fraudulent, requested_by_customer, or
abandoned) or generated by Stripe internally (failed_invoice, void_invoice,
or automatic).
