A wallet supplied different billing and delivery details

Establish what each address was meant to do

WooCommerce describes express checkout as using information already held in an existing account. That explains why a buyer may complete checkout without retyping details. It does not tell you which address the buyer selected for this order, whether it was current, or which field your installed integration saved. Start with the order and its payment reference so that every comparison concerns the same purchase.

Billing information has a payment-verification purpose. Stripe says it submits collected street-address and postal-code information for issuer verification; support varies by country and issuer. The shipping destination answers a different question: where the order is to be delivered. Do not overwrite billing with shipping merely to make the two blocks look alike. A failed address check can occur on a legitimate payment, and a payment result does not confirm a later delivery instruction.

Locate the first field that changes meaning

Compare like fields in sequence: the recorded wallet or checkout billing field with the store billing field, the recorded delivery field with the store shipping field, and the store shipping field with the fulfillment destination. Include the recipient, company or department where present, street lines, unit, locality, postal code and country. A field missing from the record is unknown; it is not evidence that the customer supplied nothing.

Keep the comparison at field level. If the order’s shipping fields agree with the recorded delivery selection but the label differs, investigate the handoff to fulfillment. If the store placed a recorded billing value in its shipping destination, the first observable mismatch is earlier. If the source value itself cannot be retrieved, you can document the store’s value and the customer’s correction, but cannot attribute the difference to the wallet.

Use records already available to authorized staff. Do not ask for a wallet login, payment credentials or an unrestricted screenshot to fill a gap. A present-day wallet address also cannot reconstruct what was selected at the time of payment.

Keep checkout-path evidence with the mapping

Record the wallet, payment extension and installed version, and whether the express button was used on the product, cart or checkout page. WooCommerce’s Stripe documentation distinguishes those paths for additional checkout fields. Its documented product and cart paths can send those additional fields empty; supported checkout-page values can be stored. Required-field validation can also occur after wallet approval.

Those documented differences justify checking the path, especially when a department or other delivery instruction was an additional field. They do not prove that a standard billing or shipping field was lost on your order. Record the field’s actual name and where it was collected before applying the additional-field explanation. Approval of the wallet sheet alone does not establish that every store field was collected or validated.

Authorize a precise correction and check the destination that will be used

Confirm through your established customer-verification process which purpose the requested address serves and exactly which fields should change. Keep the original selection, the later request and the confirmation as separate dated records. If the requester cannot be verified, keep the correction unresolved rather than treating a matching payment amount or wallet approval as authorization.

Check whether fulfillment is unassigned, prepared or already dispatched before deciding the next action. An order edit is not evidence that a prepared label or a fulfillment partner received the new destination. The authorized fulfillment owner should confirm the destination that will actually be used; an already dispatched shipment needs a separate delivery-change inquiry. Check relevant provider and fulfillment conditions before approving a change.

If the records point to repeated field-mapping errors, describe the platform, express path and first mismatched field in a Prism checkout-review consultation. Keep the actual customer addresses and payment records in your authorized systems. Scope, responsibilities, fees and terms are confirmed before work; the inquiry itself does not change an order or determine provider eligibility.

Wallet address mapping

Complete this for one genuine order before editing it. Keep full addresses in the authorized order system; enter field names, comparison results and restricted record locations here. Read from source to destination: the first unexplained difference identifies the handoff to investigate. A missing source remains unknown.

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.