# Test your integration

Test your Stripe integration before going live.

Before [going live](https://docs.stripe.com/get-started/checklist/go-live.md), test your Stripe integration to confirm it handles payments, errors, and edge cases correctly. Stripe provides *sandboxes* (A sandbox is an isolated test environment that allows you to test Stripe functionality in your account without affecting your live integration. Use sandboxes to safely experiment with new features and changes), [test card numbers](https://docs.stripe.com/testing.md), and [test API keys](https://docs.stripe.com/keys.md#obtain-api-keys) so you can simulate real transactions without moving money or processing payments through card networks.

## Test environments

A sandbox is an isolated test environment. Payments, customers, and other objects you create in a sandbox don’t affect your live integration. You can create [up to five sandboxes](https://docs.stripe.com/sandboxes/dashboard/manage.md#create-a-sandbox) to give teams separate environments, and [invite external users](https://docs.stripe.com/sandboxes/dashboard/manage-access.md#grant-users-access-to-a-specific-sandbox) without exposing live data. Access your sandboxes from the account picker in the [Dashboard](https://dashboard.stripe.com/sandboxes) or through the [Stripe CLI](https://docs.stripe.com/stripe-cli.md). Learn more about [sandboxes and the test mode sandbox](https://docs.stripe.com/testing-use-cases.md#compare).

## Test cards and simulated payments

Use [test card numbers](https://docs.stripe.com/testing.md) to simulate successful payments, [declines](https://docs.stripe.com/testing.md#declined-payments), [disputes](https://docs.stripe.com/testing.md#disputes), [refunds](https://docs.stripe.com/testing.md#refunds), and [3D Secure authentication](https://docs.stripe.com/testing.md#regulatory-cards). Test cards work with your test API keys and behave like real cards—for example, `4242 4242 4242 4242` simulates a successful Visa charge.

You can also test [non-card payment methods](https://docs.stripe.com/testing.md#non-card-payments) such as ACH Direct Debit, SEPA, and bank redirects. Each payment method has its own test values.

## Webhooks and events

Trigger test events to confirm your [webhook endpoints](https://docs.stripe.com/webhooks.md) handle notifications correctly. You can send test events from the Dashboard or with the [Stripe CLI](https://docs.stripe.com/stripe-cli.md).

[Test card numbers and values](https://docs.stripe.com/testing.md): Find test card numbers, PaymentMethods, and tokens to simulate payments, declines, disputes, and so on.

[Testing use cases](https://docs.stripe.com/testing-use-cases.md): See common testing scenarios, compare the test mode sandbox and general sandboxes, and review QA best practices.

[Sandboxes](https://docs.stripe.com/sandboxes.md): Create and manage isolated test environments for your team.

[Test Apple Pay and Google Pay](https://docs.stripe.com/testing/wallets.md): Verify your digital wallet integration works correctly.