Wallets appear twice after an express component was added

Identify two controls before calling them duplicates

Record the checkout URL, observation time, device and browser, then describe the two visible controls and their positions. Compare controls on the same page state. A wallet shown on a cart page and again on a later checkout page is a different observation from two copies visible together. A wallet logo used as informational artwork is also different from an operable payment control.

Name the actual wallet in each location and keep the observed method separate from the component name. A section labelled express checkout does not establish that the site uses Stripe Express Checkout Element. The implementer should identify the rendering component from the installed integration and its configuration. This distinction matters because Stripe’s documented deduplication applies to its composed Elements, not every pair of interfaces that displays the same payment brand.

Compare the installation with the documented arrangement

Stripe’s Payment Element documentation states that when Express Checkout Element is used alongside Payment Element, wallets appear in the express component instead of being duplicated in Payment Element. Two intentionally composed components therefore do not, by themselves, call for two wallet presentations. The standard payment component can remain part of the checkout while the express component presents the wallets.

Have the implementer map each visible location to its source: Express Checkout Element, Payment Element, or another identified integration. Record any repeated mounting or separate plugin-controlled location as an observation to investigate, not as a diagnosed cause. If the second control belongs to another plugin or a custom integration, the two-Element rule alone cannot establish how that control should be configured.

Stripe also documents dynamic payment-method display based on factors including location, currency, amount and enabled methods. Preserve those non-sensitive conditions when comparing observations. A method disappearing after a cart or configuration change does not, by itself, show that duplicate presentation was repaired.

Give the repair an explicit presentation owner

For the documented Stripe pair, specify Express Checkout Element as the intended wallet presentation location. The implementer should identify which supported setting or component arrangement corrects the extra control in the installed version. Do not choose an option simply because its name contains wallet; the documentation distinguishes options with different purposes, and the live integration determines which configuration surface applies.

Ask for a change note that names the extra control, its rendering owner, the proposed supported adjustment and the standard payment choices that should remain visible. A visual concealment alone does not establish that the component arrangement now follows the intended integration. Equally, turning off a payment method throughout the account to remove one duplicate does not answer which component should display it.

After the authorized change, compare the actual page under the recorded conditions. The useful result is one intended wallet presentation, with the expected standard payment controls still usable. Keep the observation limited to presentation; no new charge is needed to establish where a button appears, and appearance alone does not verify the entire payment flow.

Turn the map into a scoped checkout question

An unresolved row should identify a concrete missing fact: the second control’s renderer, the installed integration’s supported configuration, or the owner authorized to change it. That gives the merchant a choice between requesting a configuration correction and obtaining an implementation explanation before approving work.

For a Prism checkout-review consultation, provide the public website, the research-only products and a short description of the repeated controls. State whether the components have been identified and what help is requested. Prism’s published support includes storefront review and help with a provider’s website questions; implementation responsibilities, scope, fees and terms are confirmed before work. Follow-up is by email, and the inquiry does not book an appointment or purchase a repair.

Wallet presentation map

Complete this for one observed checkout state using the installed configuration and a dated view of the page. Unknown component ownership remains an investigation item. A completed map supports a presentation change request, not a payment or eligibility claim.

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.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.