Confirm Konbini Payment

Confirm a Konbini payment stripe.confirmKonbiniPayment(clientSecret: string, data?: object, options?: object) Use stripe.confirmKonbiniPayment in the Konbini payment flow when the customer submits your payment form. When called, it will confirm the PaymentIntent with data you provide. Note that there are some additional requirements to this flow that are not covered in this reference. Refer to our integration guide for more details. 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. 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.confirmKonbiniPayment 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. - 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. - payment_method_options An object containing payment-method-specific configuration to confirm the PaymentIntent with. - konbini Configuration for this Konbini payment. - confirmation_number An optional 10 to 11 digit numeric-only string determining the confirmation code at applicable convenience stores. May not be all 0 and could be rejected in case of insufficient uniqueness. We recommend to use the customer’s phone number. - options An options object to control the behavior of this method. - handleActions Set this to false if you want to handle next actions yourself. Please refer to our integration guide for more info. Default is true. ### with collected data ### Data argument properties - payment_method Pass an object to confirm using data collected. - billing_details The customer's billing_details. - name The customer's full name. - email The customer's email address. - payment_method_options An object containing payment-method-specific configuration to confirm the PaymentIntent with. - konbini Configuration for this Konbini payment. - confirmation_number An optional 10 to 11 digit numeric-only string determining the confirmation code at applicable convenience stores. May not be all 0 and could be rejected in case of insufficient uniqueness. We recommend to use the customer’s phone number. ### Example title Confirm with collected data ### with an existing payment method ### Data argument properties - payment_method The id of an existing PaymentMethod. - payment_method_options An object containing payment-method-specific configuration to confirm the PaymentIntent with. - konbini Configuration for this Konbini payment. - confirmation_number An optional 10 to 11 digit numeric-only string determining the confirmation code at applicable convenience stores. May not be all 0 and could be rejected in case of insufficient uniqueness. We recommend to use the customer’s phone number. ### Example title Confirm with existing payment method ### with an attached PaymentMethod ### Data argument properties - payment_method_options An object containing payment-method-specific configuration to confirm the PaymentIntent with. - konbini Configuration for this Konbini payment. - confirmation_number An optional 10 to 11 digit numeric-only string determining the confirmation code at applicable convenience stores. May not be all 0 and could be rejected in case of insufficient uniqueness. We recommend to use the customer’s phone number. ### Example title Confirm with an attached PaymentMethod ### Example title Confirm a Konbini payment