Back to home

Disclaimer

Last updated: November 2026

Test data only

MockCard is a tool for building and testing software. Every card number, CVV, expiry date, name and payment event it produces is fictitious. Generated numbers follow card-brand formats and pass the Luhn check so that test code accepts them, but no bank issued them, they are not linked to any account and they will be declined by live payment systems. Trying to use them for real purchases, identity checks, free trials or to deceive anyone is prohibited and may be illegal.

A simulation, not the real gateway

MockCard models the request and webhook formats, signatures and failure behaviour of payment gateways such as Stripe and Razorpay. Real gateways change their APIs, payloads, retry rules and timing, and their behaviour in production can differ from any simulation. Always confirm your integration in your gateway's own test mode before you go live, and follow its documentation where it differs from ours.

Scores and passing runs are not guarantees

Chaos runs, health-check scores, resilience audits and monitor results test the specific scenarios we describe. A passing run, a score of 100 or a healthy monitor means your handler behaved correctly in those scenarios at that moment. It does not mean your integration is free of bugs, secure, compliant with PCI DSS or any other standard, or that it will handle every situation a live gateway can produce.

Your systems and test traffic

Chaos runs intentionally send duplicate, late, out-of-order, declined and abandoned-payment events, and may create test orders, send emails or change stock in the system you point them at. Use development, CI or staging environments with test-mode credentials. Production monitors send only signed probes, and only to domains you have verified, but your handler needs the probe guard to skip them. We are not responsible for the effects of test traffic on systems you choose to test.

Monitoring is not an uptime guarantee

Monitors check on a schedule (hourly on Pro and Agency) and alerts depend on email and Slack delivery. Problems between checks, or alerts delayed by those services, may go unnoticed for a while. Use MockCard alongside, not instead of, your own production monitoring.

Guides and blog

Our documentation, guides and blog are general technical information, written to the best of our knowledge at the time. Some blog posts are drafted with the help of AI and reviewed before publishing. Gateway behaviour and best practice change, so content can become out of date. Check important details against your provider's current documentation.

Not professional advice

Nothing on MockCard is financial, legal, tax, security or compliance advice. Decisions about how you build, secure and operate your payment systems, and whether they meet the rules that apply to you, are yours.

Trademarks and affiliation

MockCard is independent. It is not affiliated with, endorsed by or sponsored by Stripe, Razorpay, Visa, Mastercard, RuPay, American Express, GitHub, WooCommerce, WordPress, Slack or any bank or card network. Their names are used only to describe compatibility, and their trademarks belong to their owners.

Links to other sites

We link to third-party sites and documentation for convenience. We don't control them and aren't responsible for their content or availability.

Limits of our responsibility

MockCard is provided "as is". Our responsibilities to you, and their limits, are set out in the Terms and Conditions.