How the PayPal sandbox works
The PayPal sandbox is a separate test copy of PayPal. It has pretend accounts and pretend money, and it answers the same API calls the real service does. Nothing in it can charge a real person.
What the sandbox is
PayPal gives developers a test environment so they can build and check payment code safely. When a developer signs up, PayPal creates sandbox test accounts, by default one business account and one personal account, each with a pretend balance (PayPal sandbox guide). The developer also gets sandbox API credentials, a client ID and a secret, that work only against the sandbox.
What happens in a sandbox payment
- The app signs in to the sandbox API with its sandbox credentials and gets a short-lived access token.
- It makes a normal API call, for example creating an order or sending a payout.
- The sandbox answers the way the live service would, with a real-looking id and status.
- Pretend money moves between test accounts. A developer can sign in to the test accounts to see it arrive (PayPal payouts setup).
What a sandbox payment proves, and what it does not
It proves the code talks to PayPal correctly: sign-in, the request, the response, the id, webhooks and error handling.
It does not prove that real money moved, because none did. It also does not cover live-only steps such as business account review. Any demo that uses the sandbox should say so plainly.
Sandbox versus simulated
These are different things, and honest software labels them differently.
- PayPal sandbox: a real call to PayPal's test servers, with a PayPal-issued id.
- Simulated: no call to PayPal at all. The app made up the result so the flow can be shown without credentials.
How Lowtides uses the sandbox
Lowtides is a demo of Consent Shopping: an AI shopper and a store both say yes, or no money moves. PayPal comes in only after that yes.
- After a green Handshake, Lowtides settles the purchase with a PayPal Payouts call in the sandbox.
- On yellow or red, no PayPal call is made. A held order waits for a person and a blocked order never reaches PayPal.
- The stop switch cancels payouts the receiver has not claimed yet.
- Every receipt says which it was. When a server has no sandbox credentials, Lowtides labels the payment "Simulated" and never calls it a PayPal payment.
- No card numbers. Lowtides never asks for or stores a card number.
The demo stores are fictional and the money is test money. You can run a purchase yourself and open the receipt to see the label.
If you are building your own
- Keep sandbox and live credentials in separate places, and never put either in a web page or a public repository.
- Show the environment on every receipt, so a test payment is never mistaken for a real one.
- Test the unhappy paths: declined, pending, canceled and refunded.
- Verify webhook signatures before trusting a webhook.
Related reading: why agentic commerce needs consent from both sides.
Common questions
Does the PayPal sandbox use real money?
No. The PayPal sandbox is a test environment with pretend accounts and pretend balances. No real person is charged and no real money moves.
What is the difference between a sandbox payment and a simulated payment?
A sandbox payment is a real API call to PayPal's test servers and comes back with a PayPal-issued id. A simulated payment makes no call to PayPal; the app produces the result itself and should label it as simulated.
Does Lowtides move real money?
No. The Lowtides demo uses the PayPal sandbox with test money and fictional stores, and labels a payment as simulated when no sandbox credentials are set.