Confirm Card Payment

Confirm a card payment stripe.confirmCardPayment(clientSecret: string, data?: object, options?: object) Use stripe.confirmCardPayment when the customer submits your payment form. When called, it will confirm the PaymentIntent with data you provide and carry out 3DS or other next actions if they are required. If you are using Dynamic 3D Secure, stripe.confirmCardPayment will trigger your Radar rules to execute and may open a dialog for your customer to authenticate their payment. When you confirm a PaymentIntent, it needs to have an attached PaymentMethod. In addition to confirming the PaymentIntent, this method can automatically create and attach a new PaymentMethod for you. It can also be called with an existing PaymentMethod, or if you have already attached a PaymentMethod you can call this method without needing to provide any additional data. These use cases are detailed in the sections that follow. > Note that stripe.confirmCardPayment may take several seconds to complete. > During that time, you should disable your form from being resubmitted and show a waiting indicator like a spinner. > If you receive an error result, you should be sure to show that error to the customer, re-enable the form, and hide the waiting indicator. > > Additionally, stripe.confirmCardPayment may trigger a 3D Secure authentication challenge. > This will be shown in a modal dialog and may be confusing for customers using assistive technologies like screen readers. > You should make your form accessible by ensuring that success or error messages are clearly read out after this method completes. - clientSecret The client secret of the PaymentIntent. - data Data to be sent with the request. Refer to the Payment Intents API for a full list of parameters. - payment_method Either the id of an existing PaymentMethod, or an object containing data to create a PaymentMethod with. See the use case sections below for details. - shipping The shipping details for the payment, if collected. - return_url If you are handling next actions yourself, pass in a return_url. If the subsequent action is redirect_to_url, this URL will be used on the return path for the redirect. - receipt_email Email address that the receipt for the resulting payment will be sent to. - setup_future_usage Indicates that you intend to make future payments with this PaymentIntent's payment method. If present, the payment method used with this PaymentIntent can be attached to a Customer, even after the transaction completes. Use on_session if you intend to only reuse the payment method when your customer is present in your checkout flow. Use off_session if your customer may or may not be in your checkout flow. See saving card details during payment to learn more. Stripe uses setup_future_usage to dynamically optimize your payment flow and comply with regional legislation and network rules. For example, if your customer is impacted by SCA, using off_session will ensure that they are authenticated while processing this PaymentIntent. You will then be able to collect off-session payments for this customer. - payment_method_options An object containing payment-method-specific configuration to confirm the PaymentIntent with. - card Configuration for this card payment. - cvc Use the provided cardCvc Element when confirming the PaymentIntent with an existing PaymentMethod. - network Selected network to process this PaymentIntent on. Depends on the available networks of the card attached to the PaymentIntent. Can only be set at confirm-time. - options An options object to control the behavior of this method. - handleActions Set this to false if you want to handle next actions yourself, or if you want to defer next action handling until later (e.g. for use in the PaymentRequest API). Default is true. ### with payment data from an Element ### Data argument properties - payment_method Pass an object to confirm using data collected by a card or cardNumber Element. - card Uses the provided card or cardNumber Element for confirmation. - billing_details The billing_details associated with the card. ### Example title Confirm with an Element ### with an existing payment method ### Data argument properties - payment_method The id of an existing PaymentMethod. ### Example title Confirm with existing payment method ### with an existing token ### Data argument properties - payment_method Pass an object to confirm using an existing token. - card An object of card data. - token Converts the provided token into a PaymentMethod to use for confirmation. - billing_details The billing_details associated with the card. ### Example title Confirm with existing token ### with an attached PaymentMethod ### Example title Confirm with an attached PaymentMethod ### Example title Confirm a card payment