Free Stripe-Shaped Mock API for Testing

What this is

A read-only-ish HTTP API that returns JSON in the shape of Stripe's public REST API. Same field names, same ID prefixes (cus_, ch_, pi_, sub_, in_), cursor pagination, integer cents, Unix timestamps, and a Stripe-style error envelope. Reads are deterministic — every request returns the same data, so you can pin snapshot tests. Writes return shape-correct objects but are not persisted.

Use it to: exercise the JSON shapes your code consumes, test webhook signature verification end-to-end, simulate failure modes (card_declined, rate_limited, timeouts) that are hard to trigger on real Stripe test cards, and demo a flow before you set up a real Stripe account.

Quick start

Fetch the first three charges. No auth needed.

curl https://mockapihub.com/api/stripe/charges?limit=3

const res = await fetch(
  "https://mockapihub.com/api/stripe/charges?limit=3"
);
const { data, has_more } = await res.json();
console.log(data[0].id); // -> "ch_..."

import requests
res = requests.get(
    "https://mockapihub.com/api/stripe/charges",
    params={"limit": 3},
)
data = res.json()["data"]
print(data[0]["id"])  # -> "ch_..."

Available endpoints

All paths support the cursor params limit, starting_after, and ending_before per Stripe's convention.

Webhook simulation

Send a signed, Stripe-shaped event to any public HTTPS URL you control. Combine with webhook.site or RequestBin for an instant inbox.

# 1. Grab a free inbox URL (no signup):
#    https://webhook.site/ → copy the unique URL

# 2. Tell us to send a Stripe-shaped event there:
curl -X POST https://mockapihub.com/api/stripe/webhooks/trigger \
  -H 'Content-Type: application/json' \
  -d '{
    "event_type": "charge.succeeded",
    "target_url": "https://webhook.site/<your-uuid>"
  }'

# 3. Refresh webhook.site — the signed event has arrived.
#    The Stripe-Signature header verifies against the secret below.

Limits: 10 trigger calls/min per IP, up to 5 events per call. Only public HTTPS URLs are accepted — private/internal addresses are refused at request time and again after DNS resolution.

Supported event types: charge.succeeded, charge.failed, customer.created, payment_intent.succeeded, payment_intent.payment_failed, invoice.paid, customer.subscription.created, customer.subscription.deleted

Failure simulation

The chaos query params apply to every /api/stripe/* endpoint. Use them to drive your error paths without provisioning special Stripe test cards or test clocks.

Example: curl https://mockapihub.com/api/stripe/charges?simulate=card_declined returns a real Stripe-shaped 402 with code: card_declined.

How this differs from the real Stripe API

• No persistence. Reads are deterministic; writes return a shape-correct object but the next GET won't find it.
• No real authentication. All endpoints are public. There's no sk_test_* key, no Bearer token, no idempotency key validation.
• No real money movement. Charges "succeed" because we say so. They don't hit a card processor.
• Limited resource coverage. Customers, charges, PaymentIntents, subscriptions, invoices, and webhooks only.
• Response shapes may drift. Stripe ships new fields constantly. We won't perfectly track every minor version. Last reviewed: 2026-05-13.

Common use cases

• Testing Stripe webhook signature verification without a Stripe account.
• Prototyping a checkout UI before committing to Stripe's SDK, or while waiting on an account-approval review.
• Driving the failure-handling paths in your code: card_declined, rate_limited, and timeout flows without test-card juggling.
• Deterministic CI fixtures for code that reads Stripe-shaped JSON.
• Demo environments — a sales engineer can demo a Stripe integration without keys, dashboards, or live accounts.

FAQ