Skip to content
Payments

beanstream.com

Beanstream Payments sandbox and mock API

https://www.beanstream.com/api/v1 Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
15
Collections
-
Event types
-
Start this simulation
example request
curl https://your-beanstream.slurry.io/api/v1/payments/123 \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 1.0.1.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 15.

  • POST/payments
  • GET/payments/{transId}
  • POST/payments/{transId}/completions
  • POST/payments/{transId}/returns
  • POST/payments/{transId}/void
  • POST/profiles
  • GET/profiles/{profileId}
  • PUT/profiles/{profileId}
  • DELETE/profiles/{profileId}
  • GET/profiles/{profileId}/cards
  • POST/profiles/{profileId}/cards
  • PUT/profiles/{profileId}/cards/{cardId}