Checkout reliability

Mobile checkout problems

A phone checkout is difficult when someone cannot see or use a part of the form they must complete. The on-screen keyboard can shrink what is visible, a field can lack a label, an error can fail to be described in text, the address or total can require sideways scrolling, a required notice can sit off screen, or the next control can be too small or covered. That is an interaction record. It is not a payment result, and it is not a reason to infer that a provider declined the business. Record the device, browser, time, and the obstacle you can actually see, and stop before submitting a payment. The person who maintains the checkout can investigate that record. The payment provider decides eligibility and account terms. Prism can discuss the observation in a consultation; confirm any investigation or implementation responsibilities separately. Describe the work you need. Prism will confirm scope, responsibilities, fees, and terms before work begins.

For: An owner or authorized representative of a research-use-only peptide business whose checkout is difficult to finish on a phone.

Updated 2026-09-21

Separate the obstacle from a payment result

If the person never reached a working payment control, there is no payment attempt to interpret. A decline is a result recorded after a payment method is submitted. An untouched or unusable button does not create that result.

Do not rebuild the payment setup to explain a field, total, or notice that could not be read. Collect the phone observation first. A later payment mismatch, if you already have one, is a different record and should be read from the provider and the order, not from the size of a button.

What a real phone can show

W3C's Reflow criterion says content should be presentable without two-dimensional scrolling at a width equivalent to 320 CSS pixels, except for parts that need a two-dimensional layout, such as a data table. On a phone, write whether the address lines and the order total can be read without sliding sideways. This observation is not a conformance certificate.

The Target Size criterion says a pointer target should be at least 24 by 24 CSS pixels, unless a listed exception applies: enough spacing, an equivalent larger control, an inline link, an unmodified browser control, or a layout where density is essential. Record whether the next control is hard to tap. A missed tap is not a decline.

Labels or Instructions requires a label or instruction when a control needs input. Error Identification requires that an automatically detected input error identify the item and describe the error in text. A red border without words does not meet that description. Write the label you see, or that you see none, and write the error words, or that you see none.

MDN's Visual Viewport description says the on-screen keyboard can shrink the visual viewport without changing the layout viewport. Record whether the field being typed in, or the control that continues checkout, sits under the keyboard or under a bar that stays on screen. W3C's Reflow notes also describe sticky content obscuring the page. You are recording what happened, not choosing a code change.

Record one device without placing a payment

Use a phone you control and the store's real checkout. A product may already be in the cart. Stop before submitting payment. For that pass, write the device model, operating system, browser name and version, the clock time and time zone, the checkout step, and which obstacle you saw.

A second phone is a second observation. Do not average them. If that pass was usable, write that it was usable on that device. One clear pass does not prove every phone works. Do not photograph or copy a card number, a password, or a customer record. The worksheet does not submit or save entries.

Who can change it, and what stays unknown

The maintainer of the theme, checkout extension, or hosted checkout is the person who can investigate a recorded obstacle. The payment provider is the party that can explain a payment result. Send each party the record that belongs to it. If you do not know who last changed the checkout, that owner is unknown until you ask.

On the current Prism site, a consultation can cover a storefront review, preparation for a card-processing review, or help connecting a provider's website questions to the pages involved. Scope, fees, and terms are discussed before work. A review is informational. It is not a legal opinion or a certificate. This page states no change in completed orders, no fee, and no decision about whether a provider will open an account.

Real-device checkout observation

Use one pass on one phone. Do not submit a payment to fill the sheet. Leave a row blank when you did not look. Worksheet entries are not submitted by this worksheet or saved by this site. Use only non-sensitive summaries; do not enter credentials, government identifiers, card or bank-account numbers, private receipt links, or customer details.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

Real-device checkout observation. The last column is for temporary notes.
What you check	What to write down	What this does not show	Your observation
Device, browser, and time	Model, operating system, browser and version, clock time, and time zone.	A different phone can behave differently. One pass is not a catalog of every device.	Device, browser, and time: Your observation
Keyboard or sticky bar	Whether the field in use, or the next control, is covered when the keyboard is open.	A covered control is not a payment decline and does not name the line of code that caused it.	Keyboard or sticky bar: Your observation
Visible labels	For each field you must complete, the label you can see, or that no label is visible.	A missing label does not say which extension drew the field.	Visible labels: Your observation
Error in text	The words that identify the item and describe the error, or that you see color only.	Color alone is not the text description. The note does not say the value was wrong in the provider's system.	Error in text: Your observation
Address entry	Whether the address fields can be read and completed without sideways scrolling.	Readable fields do not prove the shipping total is correct.	Address entry: Your observation
Order total	Whether the amount due can be read without sideways scrolling at the width you used.	A readable total does not prove the shipping rules are right.	Order total: Your observation
Required notice	Whether a notice your checkout is configured to require is visible before the step that depends on it.	Visibility is not a legal conclusion about which notices a provider requires.	Required notice: Your observation
Next control	Whether the control that continues is visible and large enough to tap without hitting a neighbor.	A difficult tap is not evidence that the provider refused the payment.	Next control: Your observation

These are temporary notes. Leaving or reloading this page may clear them. The consultation form does not include these entries.

Limits

A Prism consultation can help you organize the facts and discuss the website or processing question. The payment provider decides eligibility, pricing, reserves, and whether an account is opened or closed.
This page is not a conformance audit, and a completed sheet is not a certificate.
Do not submit a payment in order to fill the sheet, and do not send card numbers, passwords, or customer records.

Related guides

Sources checked 2026-09-21

W3C understanding Reflow — checked 2026-09-21. Content should remain usable without two-dimensional scrolling at a width equivalent to 320 CSS pixels, with exceptions, and sticky content can obscure the page.
W3C understanding Target Size — checked 2026-09-21. Pointer targets are at least 24 by 24 CSS pixels except for the stated spacing, equivalent, inline, user-agent, and essential exceptions.
W3C understanding Labels or Instructions — checked 2026-09-21. Labels or instructions are provided when content requires user input.
W3C understanding Error Identification — checked 2026-09-21. An automatically detected input error must identify the item and describe the error in text.
MDN Visual Viewport — checked 2026-09-21. The on-screen keyboard can shrink the visual viewport without affecting the layout viewport.
Prism solutions — checked 2026-09-21. Public support is a storefront review, preparation for a card-processing review, or help with a provider's website questions. The provider decides eligibility and account terms.
Prism features — checked 2026-09-21. A website review is informational and is not a legal opinion or a compliance certificate.
Prism contact — checked 2026-09-21. Follow-up is by email. Scope, fees, and terms are discussed before work. The form does not book an appointment, purchase a service, or submit a processing application.

Request a consultation

Describe the business and this specific question. Prism follows up by email to discuss fit and scope. An inquiry is not a processing application or an approval.

Request a consultation All resources