By platform

Test PayPal payment Shopify: start from the cart

PayPal can appear on the cart and at checkout, and each place sends a shopper to PayPal with a different amount of store data. Mimiq sends simulated visitors from the cart and shows the screen each one saw before PayPal opened.

5 visitors try to .
First test free with an accountRun it from your coding agent

How do I test a PayPal payment on a Shopify store before launch?

Open the store in a signed out browser, add an item, and start PayPal once from the cart and once from checkout. Compare the total each PayPal window shows with the total in your cart and in the order you finish, since a changed total is what a buyer checks first. A simulated visitor runs the same two starts and reports the screen before PayPal, and the test stops on PayPal's page.

What this looks like in a report

Who
Nkem, buying a canvas tote for her sister's birthday
How they arrived
Opened the shop from a search for tote bags on her laptop
Where they stopped
Cart, after starting PayPal from the cart button

“The cart showed one total, and the PayPal page showed a higher one with a shipping line I did not see before. I do not know which number is right, so I stop here.”

The fix. Move the shipping and tax estimate onto the cart page, or turn off the PayPal button on the cart, then test that the PayPal total matches the cart on a phone and a laptop.

An illustration. Run a test to see your own.See a real sample report

A PayPal button in the cart can skip the store's checkout steps

A PayPal button on the cart page can send the shopper to PayPal before the store has asked for a shipping address, a discount code or a tax region. PayPal works out some details itself, and the store has to match them when the shopper returns. If the cart total and the PayPal total differ, the shopper sees two numbers and no explanation. If the return lands on a page that does not show the order, the shopper assumes the purchase failed. The fault sits in the steps between the button and the return, and a test that starts at checkout never touches it.

  • Start PayPal from the cart and from checkout, and compare the two totals in the PayPal window.
  • Check that discount codes survive the trip to PayPal and back to the store.
  • Confirm the address PayPal returns matches the one the shopper gave, or the one you expected.
  • Note whether the return page shows the order number and a paid status.
  • Check the shipping rate PayPal shows matches the rate the store charges.

Two starts, two sets of data

A PayPal start from the cart and a start from checkout send different information. The cart start can happen before the shopper has entered an address, so PayPal may estimate shipping on its own, or leave it for the return. The checkout start happens after the store knows the address and the rate, so its numbers are more complete. Neither is wrong by itself. The problem is a shopper who sees both and cannot tell which total is the one they will pay.

Run both starts on the same cart and note every line in each PayPal window. Look at the item list, the quantity, the discount, the shipping and the total. Any line that is missing or different is a candidate for the fault, and the cart start is often the first place to look. Write each difference down with the window it came from. Repeat the comparison after each change to the cart or the shipping rules.

The return trip is where orders go missing

After PayPal, the shopper comes back to the store, and the store decides what to show. If the return page lacks the order number, the shopper may think nothing was bought and start again. If the cart still holds the items, the shopper may try to pay again. A return that lands on a clean confirmation page is the one a buyer trusts. Check which of those outcomes the return gives, using a test order rather than a screenshot of the button.

In the store admin, check that the order exists, shows as paid and lists the items and totals the shopper saw. A missing order after a successful PayPal payment is usually a notification fault, not a cart fault, and it needs a different fix. Write down which screen the shopper saw after the return, so a support message can say exactly what happened.

The screens a visitor can read before PayPal takes over

A simulated visitor starts PayPal from the cart, then from checkout, and records each window it opens. It stops on PayPal's page because a visitor has no PayPal account to finish with. The screenshot records whatever the window shows before the test stops, including any total it displays, but the test does not reach the return to your store. Finish the return with a sandbox buyer account or one small live order you refund, and read the return page yourself.

Mimiq is independent and not affiliated with the platforms it names. Names belong to their owners.

What you get with Mimiq

  1. 01

    Run it by hand, or on every pull request

    Paste a link and a task in the app and watch the visitors work. Or run them on every preview deploy: the GitHub Action comments on the pull request, any other CI can call the MCP endpoint, and your coding agent can run it too.

  2. 02

    Bugs and usability problems in one report

    The browser records errors and failed or slow requests on the step they happened. The visitors say where the wording or the steps confused them, and where they left.

  3. 03

    Visitors that behave like your audience

    Each visitor is a different profile with a reason to be there, matched to who the page is for, described by you, or built from your own customers.

  4. 04

    A prompt to fix each problem

    Every problem comes with a fix to paste into Cursor, Claude Code, Lovable or any coding agent, and one prompt hands over the top problems at once. Then send the same visitors through again.

  5. 05

    Follow every visitor

    See each visitor's whole path, step by step with screenshots, and what it was thinking at every step. Ask any visitor a question.

The browser records relevant JavaScript errors and failed or slow app requests encountered during the run, attached to the step where they occurred. The visitors are simulated: they find problems, they do not predict how many real people will convert.

A discount app or shipping rule change can break the cart button

A new discount app, a shipping rule or a theme update can change what the cart sends to PayPal without any visible change on the cart page. Rerun both PayPal starts with the same cart after each of those changes, and compare the totals line by line. Check the return page with one test order each time, since a changed total is easy to miss in the cart.

Starter

Try it on one launch

$9 once
120 credits, never expire

About 4 tests of 5 visitors

  • Visitors on your landing page, signup and checkout
  • Where they left and why, with a fix to copy for each problem
  • Run it in the app or on every pull request
  • Ask any visitor a question, included
  • Test accounts and protected previews
Buy 120 credits

Builder

Test every build

$19 a month
500 credits every month

About 20 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Builder

Pro

Test every release, as a team

$49 a month
1,500 credits every month

About 60 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Pro

Scale

Test at scale, every day

$149 a month
6,000 credits every month

About 240 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Priority support
  • Cancel anytime
Choose Scale
$0for your first test, with a free account (Google sign-in, no card). It includes 50 credits, enough for 10 visitors. After that a visitor uses 5 credits, and packs start at $9 for 120 credits.
See a sample report

Questions

Can a simulated visitor pay with PayPal?

No. A visitor has no PayPal login, and the test does not go past PayPal's page. The test shows the button, the window and the cart total before PayPal. Finish the payment with a sandbox buyer or one small live order that you refund.

Should I remove the PayPal button from the cart?

Not by default. Remove it only if the cart start shows totals or addresses that differ from checkout and you cannot fix the difference. Otherwise keep it, since the checkout start has more details filled in and matches what the shopper will pay.

Why does PayPal show a different total from my cart?

One common cause is that PayPal received a shipping or tax figure the cart does not show yet, or a discount applied in one place only. Compare the two totals line by line before you change anything, and note which line differs.

Will the test tell me how many shoppers use PayPal?

No. The test cannot tell you how many shoppers pick PayPal over a card, or how many finish once they reach it. It shows whether the button starts the trip and what each visitor saw before PayPal. Use your order data for those rates.

What do I check after the return to the store?

The order number, the paid status in the admin, whether the cart cleared and a confirmation email if you send one. A return page that shows nothing is the screen a buyer reads as a failure, so check it on a phone as well as a laptop.

Keep reading

Send visitors and see what breaks first.

Your first test is free: sign in with Google and it starts right away. Last checked 2026-11-02.

5 visitors try to .