Go beyond a successful purchase
Run a complete scenario. Exercise refunds and state changes that a fixed sample response cannot cover.
Payments SimulatorHopper Labs
Put your payment flow through its paces.
Run a purchase, issue a refund and inspect the events in between. Repeat the scenarios your application needs to get right.
What makes it useful
Test the awkward payment paths, too.
See the sequence of events
Inspect transitions. Trace what happened between a request and the final payment state.
Repeat the failing scenario
Repeat a case. Run the same sequence again while you fix the application that consumes it.
Useful alone. Better together.
Test the flow in a wider business story.
Exercise a storefront payment scenario and follow its simulated events into the records that depend on them.
A closer look
See what you can do.
The capability, the action, and what it means for you.
| Feature | What you can do | Why it matters |
|---|---|---|
| Stateful purchases and refunds | What you can doRun a complete scenario. | Why it mattersExercise refunds and state changes that a fixed sample response cannot cover. |
| Event history | What you can doInspect transitions. | Why it mattersTrace what happened between a request and the final payment state. |
| Scripted scenarios | What you can doRepeat a case. | Why it mattersRun the same sequence again while you fix the application that consumes it. |
3 capabilities
Practical details
- Experience
- Interactive browser demo
- Data
- Temporary demonstration session
- Availability
- Demonstration available; release availability is separate
Trying the experience
An isolated demonstration session. No production accounts are connected.
- Open Simulation and run the sample purchase and author payout.
- Inspect Transactions, Connect accounts, transfers and payouts.
- Refund a payment, then inspect its events in Developers / Workbench.
Payments Simulator