The shipping charge changed inside the wallet sheet

Recover one journey without filling in missing stages

Use the records from the reported checkout, not the rate currently remembered by staff. Note the express method, the page where the buyer opened it, the time and the installed WooCommerce and payment-extension versions. A product-page button, a cart button and a checkout-page button are different entry points worth identifying in the handoff.

Place available observations in order. A contemporaneous cart view, wallet view and completed order can establish what each displayed. A buyer’s recollection can identify the symptom but should remain labeled as a report when no capture exists. If the final order is the only saved amount, it does not reconstruct every value the wallet showed. Leave missing stages unknown instead of describing a change nobody recorded.

Compare destinations and delivery choices before comparing prices

WooCommerce’s Stripe express-checkout documentation says express methods use information prefilled from an existing account. That makes the destination actually shown in the wallet a separate fact to check against the cart destination. Do not assume that a remembered cart address and the wallet’s selection are identical.

WooCommerce shipping zones match the shipping destination to one zone, using the first matching zone in the configured order. The customer sees that zone’s methods. Record the zone match for each observed destination and the specific delivery option selected at each stage. The same general delivery label is insufficient if it refers to different configured methods.

Compare full addresses only inside authorized customer records. In the worksheet, record whether the destinations matched and which zone applied, without copying the buyer’s address. If the destination or method changed, you have identified a material input difference. That does not yet prove the returned price was correct or that the wallet caused the change.

Keep the shipping line distinct from the payable total

For every observed stage, record the shipping amount separately from the total, preserving currency and whether any tax was shown separately. Retain the actual item quantities and any displayed discount alongside the comparison. If a view shows only a total, mark the shipping component unavailable; do not derive a supposed shipping charge by subtracting figures taken from a different stage.

Compare the final wallet amount with the store order’s shipping line and total, then compare the order total with the matching provider payment amount and its actual state. Use the payment linked to that order, not a net payout containing other movements. A wallet display alone does not establish what amount was ultimately taken.

The useful finding is where two observed records stop agreeing. If the final wallet total and payment match but the earlier cart differs, focus on the inputs and displays before confirmation. If the final wallet evidence and order disagree, preserve both for the integration investigation. If the order and provider amount disagree, keep that payment reconciliation explicit rather than treating it only as a rate-setting problem.

Choose the next check from the first supported difference

When the destination differs, check the two zone matches and the choices actually offered. When the destination matches but the selected method differs, inspect that selection against the configured methods. When both match and the price differs, identify the component supplying the rate and preserve its version and available calculation record. Core shipping-zone rules do not explain an extension or carrier formula on their own.

The express-checkout evidence establishes prefilled information and path-specific behavior, not a universal sequence in which every wallet recalculates and updates every amount. Do not fix an assumed sequence by changing rates globally, removing validation or treating wallet approval as proof of a completed order. The investigation should name the earliest supported discrepancy and the missing record that would explain it.

For a Prism checkout-review consultation, describe the express method, entry page, observed input difference and the two amounts that failed to agree. Keep customer records in their authorized systems. Confirm scope, implementation responsibilities, fees and terms before work; technical compatibility does not establish payment-provider eligibility for the business.

Wallet shipping-total trace

Use one real checkout journey. Record only stages supported by an actual record or clearly labeled buyer report. A blank stage is a visibility gap, not evidence that the amount stayed the same. Compare full addresses privately and enter only match results here.

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.