> ## Documentation Index
> Fetch the complete documentation index at: https://docs.solvapay.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Test in sandbox

> Use sandbox mode to test your integration before or after live activation.

## Prerequisites

Before testing, make sure you have:

* Created your first product
* Configured pricing plans during product creation
* Chosen your integration path (no-code MCP integration or SDK)

If you are on the SDK path, run [`npx solvapay init`](/sdks/typescript/setup/cli) first so your
project is connected before endpoint testing.

## What is sandbox mode?

In sandbox mode:

* No real charges are processed
* Stripe test mode is used for all payment flows
* You can create test customers and purchases freely
* All data is separate from production

You can see your current mode in the console header.

You can switch between **Live** and **sandbox** at any time. Many providers activate live first, then switch back to sandbox for safe testing and regression checks.

## Testing your integration

### For the no-code MCP integration

1. **Add your proxy URL to an MCP client**

   Copy the proxy URL from the no-code MCP integration section and add it to your MCP client (e.g., Cursor, Claude Desktop).

2. **Complete the OAuth flow**

   When you first use a tool, you'll be prompted to sign in. Use your Google or GitHub account.

3. **Test tool access**

   Call a protected tool and verify it succeeds. Check the dashboard to see the usage recorded.

4. **Test plan restrictions**

   Try calling a tool that requires a paid plan. You should receive an access denied response with upgrade information.

### For SDK integration

1. **Run the CLI setup**

   From your project root, run `npx solvapay init` if you have not already.

2. **Use your sandbox API key**

   Your sandbox API key is available in Settings > API Keys. Use this in your development environment.

3. **Create a test customer**

   Use the SDK or console to create a customer for testing.

4. **Test paywall protection**

   Call a protected endpoint and verify the paywall check runs correctly.

5. **Test the checkout flow**

   Trigger a checkout and use Stripe test card numbers to complete the payment.

## Live MCP client testing

For live authentication and paywall validation in Claude or Cursor, use
[Test MCP server auth and paywall](/mcp-server/testing-auth-and-paywall).

## Stripe test cards

Use these card numbers for testing payments:

| Card number           | Result                   |
| --------------------- | ------------------------ |
| `4242 4242 4242 4242` | Successful payment       |
| `4000 0000 0000 0002` | Card declined            |
| `4000 0000 0000 3220` | 3D Secure authentication |

Use any future expiration date and any 3-digit CVC.

## Testing checklist

Before or after going live, verify:

* [ ] Users can authenticate (OAuth for the no-code MCP integration, your auth for SDK)
* [ ] Free plan users can access free tools/endpoints
* [ ] Paid tools are blocked for free users
* [ ] Checkout flow completes successfully
* [ ] After payment, users gain access to paid features
* [ ] Usage is tracked correctly in the dashboard
* [ ] Quota limits are enforced when exceeded

## Next steps

Once you've verified your integration works correctly:

* [Go live](/get-started/go-live) - Complete onboarding and switch to production