Stripe Card Test Link: Test Mode Payment Link Guide

What a Stripe test card link is

A Stripe test card link is a payment link generated while the dashboard sits in test mode. It behaves like a live link, but it only accepts the test card numbers Stripe publishes in its documentation. No real card is charged, no money moves, and the resulting objects are isolated from your live account. Test mode is tied to API keys that carry the sk_test_ and pk_test_ prefix, so a link created in test mode cannot accept a live payment and a live link cannot be exercised with test numbers.

This matters for two reasons. First, you can verify checkout, redirect, receipt, and webhook behavior end to end before you ship. Second, you never have a reason to type real card data into a testing flow, which keeps sensitive card data out of your development environment entirely.

Before you begin

• A Stripe account with dashboard access
• Test mode switched on, confirmed by the orange test banner
• A browser profile you use for development
• Your webhook endpoint or the Stripe CLI forwarding events

Create the test link

1. Sign in to the Stripe dashboard.
2. Toggle Test mode on using the switch at the top of the page.
3. Open the Product catalog and create a product with a price if you do not already have one.
4. Go to Payment links and select New.
5. Choose the product and price you just created.
6. Set the collection options you want, such as email, promo codes, or shipping address.
7. Save the link and copy the generated URL.
8. Open the URL in a private browser window.
9. Enter 4242 4242 4242 4242 as the card number.
10. Enter any future expiry date, any three digit CVC, and any five digit postal code.
11. Submit the payment and confirm the success page appears.
12. Return to the dashboard, open Payments, and confirm the test payment appears with a test badge.

Test card numbers that cover the common paths

• 4242 4242 4242 4242: standard Visa success
• 4000 0025 0000 3155: triggers 3D Secure authentication
• 4000 0000 0000 9995: declined for insufficient funds
• 4000 0000 0000 0002: generic decline
• 5555 5555 5555 4444: Mastercard success

Run the decline numbers as well as the success numbers. A checkout that only handles the happy path will break the first time a real card is rejected.

Verify the result

Open the payment detail page and check three things: the payment status, the event log for that payment, and whether your endpoint received the matching event. For the 3D Secure card, the test challenge page appears inline and you choose whether to complete or fail it, which lets you rehearse both branches of your authentication handling. If you are testing subscriptions, confirm the subscription object and the first invoice were created as expected.

Rules to keep the test clean

• Never enter a real card number into test mode. It will not process, and entering it exposes card data to your logs.
• Never store full card numbers or CVC values in application logs, error reports, or database columns.
• Keep test keys out of production builds and production keys out of local environments.
• Rotate any key that was pasted into a shared document, chat thread, or screenshot.

Purchasing or trading card numbers is illegal in the United States and most other jurisdictions, and those numbers fail in test mode anyway. The only card values that belong in a test flow are the ones Stripe publishes for that purpose.