![]() You can refer to the payment methods documentation for more details about how to handle their required next actions. You can find a full list of possible next actions in the API documentation. ![]() The type of possible next actions can differ between various payment methods. The PaymentIntent’s next_action property exposes the next step that your integration must handle to complete the payment. Stripe.js handles these automatically when confirming the PaymentIntent, but if you have an advanced integration, you might want to handle these manually. Some payment methods require additional steps, such as authentication, to complete the payment process. Note that in addition to the final successful charge, the list includes any unsuccessful charges created during the payment process. To view all of the charges associated with a PaymentIntent, list all charges with the payment_intent parameter specified. For example, If a datacenter is drained, then dont alert me on its latency is one common datacenter alerting rule. retrieve ( '' )Ī PaymentIntent’s Charge property only contains the most recent charge. The following list describes how to handle webhook events: ![]() Reuse the same PaymentIntent to continue tracking the customer’s purchase. The GUI is color-coded so you can easily see elements that. Through the user network interface, you can monitor your Current Network Status with your Host Status Totals and Network Service Status Totals broken down at the top of the page. You can notify the customer that their payment didn’t complete and encourage them to try again with a different payment method. Nagios Core is an open-source network monitor that has a web interface for monitoring network performance. When payment is unsuccessful, you can find more details by inspecting the PaymentIntent’s last_payment_error property. # Notify the customer that payment failed end Puts "Succeeded:", intent # Fulfill the customer's purchase when 'payment_intent.payment_failed'Įrror_message = intent & intent Status 400 return end case event when 'payment_intent.succeeded' Status 400 return rescue Stripe : : SignatureVerificationError = > e The following are some possible statuses of the PaymentIntent following a confirmation: To check the status of a PaymentIntent without using the confirmCardPayment function, retrieve it independently by using the retrievePaymentIntent function and passing in the client secret. Check PaymentIntent status on the client without using confirmCardPayment When the payment requires an additional step such as authentication, the promise doesn’t resolve until that step is either complete or has timed out. When it completes successfully and returns a PaymentIntent, the status is always succeeded (or requires_capture if capturing later). The promise returned by confirmCardPayment resolves when the payment process has either completed or failed with an error. The customer’s payment failed on your checkout pageĭisplay an error message and prompt your customer to attempt payment again Inform the customer that their payment succeeded The customer completed payment on your checkout page
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |