Skip to content
On this page

Start here

Test cards and test mode

Try everything without real money: the simulated bank, test cards for every outcome, and tools that run renewals and chargebacks now instead of waiting.

How test mode works

  • Every business starts in test mode. Switch between Test and Live at the top of the dashboard once the business is live.
  • Test and live data are separate: products, customers, subscriptions, keys and webhook endpoints of one mode are never visible in the other. sk_test_… keys see only test data.
  • Payments go to Cycle's simulated bank. Nothing is charged and no real card is needed.
  • Emails to test customers go to the business owner's address, so you can see them without bothering anyone.
Your bank's test environment
Once you save the test logins your bank gave you (in onboarding), test payments go to your bank's own test environment instead of the simulated bank.

Test cards

Use any future expiry date and any CVC. When a card asks for 3-D Secure, the code is 111111. A saved card keeps its behaviour on later charges, so you can test renewals and recovery.

Card numberBrandWhat happens
4242 4242 4242 4242VisaApproves, including later renewals
5555 5555 5555 4444MastercardApproves (Mastercard)
9051 0000 0000 0003ArCaApproves (ArCa)
4000 0000 0000 0002VisaDeclined: card declined
4000 0000 0000 9995VisaDeclined: insufficient funds
4000 0000 0000 0069VisaDeclined: expired card
4000 0000 0000 3220VisaRequires 3-D Secure (code 111111), including on renewals
4000 0000 0000 0341VisaFirst payment approves; later charges of the saved card fail
4000 0000 0000 0119VisaFirst payment approves; later charges go through but the bank's reply is lost (the follow-up check finds them)

Run renewals now

Renewals normally wait for the end of the period. In test mode you can run the next one now, exactly as it would run on the day: a trial ends, an active period renews, a past-due subscription gets its next retry.

  • In the dashboard: open the subscription and choose Run the next renewal now.
  • With the API: POST /api/v1/test/subscriptions/{id}/renew (test keys only). See the endpoint.

To see a failed renewal and its recovery: subscribe with 4000 0000 0000 0341 (the first payment works, later charges fail) and run the renewal. The subscription becomes past_due and subscription.past_due and payment.failed are sent. Then change the card to 4242 4242 4242 4242 in the customer portal and run it again: subscription.recovered.

Simulate a chargeback

Open a succeeded test payment and choose Simulate a chargeback. A dispute opens as if the customer had disputed the payment with their bank, dispute.opened is sent, and you can answer it and decide it from the dispute's page (dispute.closed).

Test your webhooks

  • Open an endpoint under Developers and choose Send test event: Cycle sends a signed ping event.
  • Every attempt, with your response, is under Developers → Deliveries, where you can send any delivery again.
  • Cycle can't reach localhost. While developing, use a public tunnel URL, or read events with GET /api/v1/events and pass them to your handler.

Before you go live

  • A paid checkout, a declined card, a renewal, a failed renewal and its recovery, and a cancellation all behave as you expect.
  • Your webhook handler rejects a wrong signature and processes each event id once.
  • Your secret keys are only on your server, in environment variables, never in git.
  • Your live endpoint uses https://, and your live keys, prices and webhook secret are in the production environment.