Two provider customer records use the same email

Start with the store identity and its actual order links

Open the store user through the store's authorized administration process. Record its internal reference and inspect the orders actually linked to it. Search results found by email can help locate candidate orders, but record whether each order has an account association or is a guest order. Do not convert the search result into an ownership decision.

WooCommerce documents guest checkout separately from account creation. Its accounts settings allow a buyer to check out without a WordPress user account. That distinction matters when the same address appears in an account and in older orders: the email does not, by itself, tell you how those orders became associated with the account. Check the current recorded association instead of assuming a historical guest purchase used today's login.

For each relevant order, follow the provider payment reference that the integration recorded. Retain the order-to-payment link even if the customer names or contact fields look identical. The purpose is to establish which records the store actually used, not to select the customer record with the most familiar display name.

Locate the saved method's recorded attachment

Stripe's save-and-reuse guide says a method prepared for future payments is attached to an object representing the customer. The guide covers Customer objects and customer-configured Account objects. Use the representation and identifiers your actual integration records; this is not an instruction to change API models or create another customer.

Compare the customer reference on each relevant payment with the reference linked to the store user and the attachment shown for the saved method. Keep the provider account context beside these references. Two records in different provider accounts cannot be treated as one record merely because their contact details match.

A payment-method attachment establishes where the provider currently records that method. It does not, on its own, establish which store user should be allowed to use it. Likewise, an earlier payment associated with one customer record does not prove that a method saved under another record may be moved. Record a missing association as unknown; do not resolve it by copying a credential.

Classify agreement, a missing link or a conflict

When the store user, relevant order payments and saved-method attachment consistently point to the same customer representation, you have a documented association for that checkout path. Preserve the evidence. The second email match alone does not show a defect that requires deletion or merging.

When the store user points to one representation and the saved method points to another, name that precise conflict. When an order is a guest order or has no recoverable customer reference, name the missing link. These findings need different resolutions; neither justifies choosing the older record, the newer record or the record with more orders as the owner.

Before a proposed correction, identify the merchant's authorized decision owner and the integration or provider owner who can confirm the supported action. Keep the original references and the reason for any approved change. Do not delete the apparently unused record while its connection to past orders remains unresolved.

Identity evidence does not expand saved-payment consent

Stripe separately limits reuse to the purpose agreed with the customer and requires a retained record of consent for the described future use. Finding a technical attachment does not authorize a different person's use, an offline charge or a broader billing arrangement. Saving a method is also separate from making a payment.

For a Prism checkout-review consultation, describe the platform, the conflicting associations and the work you want scoped. Keep the detailed customer map in your authorized internal system; the public inquiry needs a non-sensitive summary. Prism will confirm scope, responsibilities, fees and terms before work. The consultation does not itself authorize a credential move, and the provider retains its account-eligibility decisions.

Store-to-provider customer map

Complete one map for the affected store account, adding separate internal entries for each candidate provider customer and order. Use internal references, not customer contact details or payment credentials. Agreement documents an association; any missing or conflicting link remains unresolved until the authorized owner confirms the supported correction.

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.