Stripe
live · conformance passing
Models the narrow slice of the Stripe API an ecommerce agent actually drives — customers, payment methods from Stripe's test tokens, payment intents through the whole status machine with manual and automatic capture, the charges behind them, balance transactions whose fee arithmetic always reconciles, refunds, disputes with real evidence deadlines, products and prices, payouts that group the available balance, and an event log with Stripe's own type strings — with bracket-nested form encoding exactly as stripe-python sends it, the one error envelope every SDK exception class is built on, idempotency that replays and refuses the way production does, and cursor pagination in Stripe's clamped-limit dialect. What stripe-mock cannot do is the point: this twin remembers the charge you made, declines a payment and then succeeds the retry, lets a dispute deadline pass unanswered and moves money from pending to available when time advances.
- Category
- Payments
- Environment key
- sk_test_…
- Verified against
- stripe 15.6.1
- Replaces
- stripe-mock's spec-shaped fixtures, which remember nothing and have no clock
What it models
Records your code can read, write and edit for the life of the environment. A route the twin does not model returns a provider-shaped refusal rather than a plausible response.
- account
- customers
- payment_methods
- payment_intents
- charges
- refunds
- disputes
- balance_transactions
- payouts
- products
- prices
- events
- idempotency_keys
Verified in CI against
- pythonstripe15.6.1