PayPal Sandbox Card Test Software: Setup and Testing Guide

What PayPal Sandbox Card Test Software Does

PayPal Sandbox card test software generates fake credit card numbers that authorize only inside PayPal's test environment. It lets you run a full card checkout, capture, refund, and decline path without moving real money. The card generator lives inside the PayPal Developer Dashboard, so you do not need a third-party tool or a live merchant account to start.

Two parts matter. The card number supplies the funding instrument. The sandbox app credentials supply the API access. Both must belong to the same sandbox environment, or the transaction fails before it reaches the card network.

Prerequisites

• A PayPal account with developer access
• Access to the PayPal Developer Dashboard
• A sandbox app with a client ID and secret
• One sandbox personal account for the buyer and one sandbox business account for the seller
• A test checkout page or API client that accepts a card number

Steps to Set Up Sandbox Card Testing

1. Sign in to the PayPal Developer Dashboard with the account you want tied to the sandbox.
2. Switch the environment toggle from Live to Sandbox.
3. Open Apps and Credentials, create an app, then copy the sandbox client ID and secret.
4. Create a personal sandbox account for the buyer role.
5. Create a business sandbox account for the seller role.
6. Open Testing Tools and select Credit Card Generator.
7. Choose the card brand you want to test, then generate the number.
8. Record the generated number, the expiry date, and the CVV shown by the tool.
9. Load your test checkout page with the buyer sandbox account signed in.
10. Paste the card values and submit the payment.
11. Confirm the result on the seller account's sandbox Activity page.
12. Repeat with a different generated card to exercise a decline or a refund.

What You Can Simulate

• Successful authorization and capture
• Declined authorization
• Full refunds and partial refunds
• Currency conversion between buyer and seller
• Expired card and invalid CVV responses
• Address verification (AVS) mismatches in supported regions

Behavior differs by region. Some legacy test numbers printed in older documentation no longer authorize, which is why the generator is the dependable source. Generate a fresh card for each test run instead of recycling a number that has already been charged.

Common Failure Modes

• Live credentials pointed at sandbox endpoints, or the reverse
• Buyer and seller sandbox accounts from different environments
• Card brand not enabled for the seller account's country
• Expiry date set in the past
• 3D Secure challenge not handled by the test client
• Sandbox account left restricted after repeated failed attempts

Security Rules for Test Data

Sandbox cards authorize only against PayPal's test environment. They carry no funds and no value outside it, so they are useless anywhere else.

1. Keep test cards in sandbox tooling and never in a production database.
2. Tokenize card data at the point of capture so your servers never hold a primary account number.
3. Separate sandbox secrets from live secrets in your config and your build pipeline.
4. Rotate sandbox client secrets after sharing a test environment with contractors.
5. Log a transaction ID and a response code instead of the card number.