Stripe and Clover test data

Use these provider-approved details only on a Strata-assigned Stripe or Clover test flow. Never enter real identity, card, or bank information.

Before you start

  1. 01

    Confirm the test page

    Check the business, assigned task, payment amount when applicable, and provider before entering anything.

  2. 02

    Run only your assigned scenario

    Do not test refunds, voids, duplicate submissions, or extra payment methods unless Strata asks you to.

  3. 03

    Stop when something does not match

    Send the page URL and what you saw. Do not try a real payment method to get around a test failure.

Stripe

Test cards, US bank accounts, and connected-account onboarding details for Stripe-hosted sandbox pages.

Card details

Use expiration 12/34, CVC 123, and ZIP code 27601.

  • Scenario

    Successful card payment

    Use

    4242 4242 4242 4242

    Expected result

    The payment is accepted.

  • Scenario

    Declined card

    Use

    4000 0000 0000 0002

    Expected result

    The page shows a safe decline and allows another attempt.

  • Scenario

    Authentication challenge

    Use

    4000 0025 0000 3155

    Expected result

    Stripe asks for test authentication before completing payment.

For the authentication challenge, follow Stripe's test prompt and choose the successful completion option unless your assigned scenario says to test failure.

Bank account details

Choose Bank account. If Stripe asks you to pick an institution, select Test (Non-OAuth). If manual entry is offered, use routing number 110000000 and the assigned account below.

  • Scenario

    Successful ACH payment

    Use

    000123456789

    Expected result

    The account is accepted. The payment can process before it succeeds.

  • Scenario

    Insufficient funds

    Use

    000222222227

    Expected result

    The payment later fails for insufficient funds. Use only when assigned.

If Stripe requests microdeposit verification, enter 32 and 45 cents. If it requests a statement descriptor code, use SM11AA. A bank payment can remain in Processing after checkout, so do not submit it again unless asked.

Connected account setup

Use these only when Strata asks you to connect a Stripe sandbox account. Use the synthetic customer profile below for ordinary name, business, email, phone, and location fields.

  • Scenario

    SMS verification code

    Use

    000-000

    Expected result

    Stripe accepts the test phone verification.

  • Scenario

    Date of birth

    Use

    1901-01-01

    Expected result

    Stripe records a successful date-of-birth match. The verification update can arrive by webhook.

  • Scenario

    SSN last four

    Use

    0000

    Expected result

    Stripe records a successful identity match.

  • Scenario

    Full personal ID number

    Use

    000000000

    Expected result

    Use this only when the test form asks for the full ID number.

  • Scenario

    Address line 1

    Use

    address_full_match

    Expected result

    Use with Raleigh, NC 27601 for a successful address match.

  • Scenario

    US payout bank account

    Use

    110000000 / 000123456789

    Expected result

    The connected account can receive a successful test payout.

If Stripe requests an identity document, use only Stripe's official test images or stop and contact Strata. Never upload a real government ID.

Clover

Test cards for an assigned Clover sandbox merchant and hosted or manual card-entry flow.

Card details

Use expiration 12/34, CVV 123, and ZIP code 27601.

  • Scenario

    Successful card payment

    Use

    4242 4242 4242 4242

    Expected result

    The payment is approved in the Clover sandbox.

  • Scenario

    Declined card

    Use

    4005 5717 0222 2222

    Expected result

    Clover returns a decline and the order must not appear paid.

Keep the assigned amount

Clover can use transaction amounts to trigger sandbox responses. Changing the amount can change the result.

Device testing uses test cards

For tap, insert, or swipe, use only the physical card supplied with the Clover Dev Kit. Never use a real card.

Clover Ecommerce sandbox does not send provider receipt emails. A missing Clover receipt is not by itself a failed transaction. Project notifications are a separate result.

Synthetic customer

Use these values when the test does not require a real email delivery. Use your assigned tester address for login codes, receipts, or notification tests.

Name
Taylor Test
Business
Example Client Test
Email
taylor.test@example.com
Phone
202-555-0147
Address
100 Test Way
City, state, ZIP
Raleigh, NC 27601

Report a result

Send one result for each assigned scenario. Include these details so the problem can be reproduced without collecting sensitive information.

  1. 01Scenario tested
  2. 02Date, time, and time zone
  3. 03Page or step
  4. 04Expected result
  5. 05Actual result
  6. 06Whether you could continue
  7. 07Provider reference or last four digits, if shown

Before attaching a screenshot, cover personal information, login codes, full payment details, and unrelated browser tabs. Report only the last four digits of a test card.