Skip to main content
No. Sandbox Pay is intended only for PayPal Sandbox, Stripe test mode, and local development. The values must not be used on production checkout pages or for real purchases.
No. Random card numbers are generated locally with a valid Luhn checksum and appropriate network prefix. A valid checksum only makes the number structurally valid; it does not represent a funded account.
A provider may require one of its documented static test cards or a specific account configuration. Select a scenario designed for the current provider rather than assuming every Luhn-valid number will be accepted.
The page may use different selectors, a custom component, or secure cross-origin iframes that content scripts cannot access. Confirm that the hostname is supported, then copy and paste any missing values manually.
The current content-script matches cover PayPal, PayPal Sandbox, Stripe, localhost, 127.0.0.1, and *.appspot.com. The manifest does not declare access to every website.
They supply provider-specific values used to exercise declined or validation-error paths in PayPal Sandbox, such as insufficient funds, expired card, suspected fraud, or CVV failure.
Country, cardholder name, card backgrounds, and other preferences are saved in browser extension storage on the current browser profile.
Sandbox Pay is a test-data helper and the Firefox manifest declares no required data collection. Do not enter real card data into the extension or use it on production payment pages.
Yes. Chrome uses the Manifest V3 side panel, while Firefox uses its sidebar action. Install the official store version for normal use; build commands are available for development.
Open an issue in the Sandbox Pay repository. Include the browser, extension version or commit, provider, test page type, expected behavior, actual behavior, and redacted screenshots. Never publish real card or customer data.