How is checkout conversion rate measured?
Pick a clear starting event, such as the checkout or payment page opening, and count each session once, however many payment attempts it contains. Then count the sessions that end with a successful payment. Retries inside one session should not inflate the denominator, and sessions that end without any outcome should stay in it. Stripe notes that incomplete payment attempts are useful for understanding conversion at checkout, which is why it lets them stay open rather than forcing a cancellation.
Why does it matter?
It ties payment performance to revenue. As an illustrative example: 20,000 checkout sessions start in a month. 2,400 customers leave before choosing a method, 1,100 drop out during authentication and 1,500 are declined and do not retry. That leaves 15,000 successful payments, a checkout conversion rate of 75%, and three different problems to work on: method coverage, authentication and approvals.
What moves it?
Showing the methods customers expect in their country, prices in their currency, fewer fields, saved cards for returning customers, authentication that is mostly frictionless, and a second chance after a decline, either another route or another method. Every change should be measured on the same definition of a session, or improvements cannot be compared.
Where does Omno use it?
Omno’s hosted checkout shows methods according to eligibility rules by country, method, currency, customer group and customer verification level, and lets a customer choose another method after a decline. Abandoned sessions receive no final webhook, so Get Transaction Info is used to reconcile them, and the dashboard’s real-time success metrics show outcomes by provider, method and country.