I’d like to suggest a valuable addition to the Bogus Gateway
that would greatly benefit developers and merchants building
fraud prevention workflows.
**The Problem:**
Currently, there’s no way to simulate a “High Risk” order
in a development store. When building Shopify Flow automations
to cancel or hold high-risk orders, merchants have no reliable
way to test whether their workflows are functioning correctly
before going live.
**The Suggestion:**
Add a dedicated test card number to the Bogus Gateway that
automatically triggers a “High Risk” fraud classification
upon order creation — similar to how specific card numbers
already simulate payment success or failure.
For example:
Card number `1` → Success
Card number `2` → Failure
Card number `5` → High Risk order (proposed)
**Why This Matters:**
Allows merchants to safely test fraud automation workflows
Reduces risk of untested Flow configurations in production
Especially critical for digital product stores where
delivery is instant and losses from fraud are immediate
Aligns with Shopify’s existing Bogus Gateway philosophy
of simulating real-world scenarios
This would be a low-effort, high-impact addition that
improves the developer and merchant experience significantly.
Hey @NarutoX, you can already flag a dev-store order as high risk today without waiting on a new Bogus card. Risk assessments are a separate object from the payment, so anything with write_orders can create one: place a normal Bogus Gateway order, then call the orderRiskAssessmentCreate mutation with riskLevel HIGH from an app using an offline token. If you’d rather stay out of the API, Flow has a “Create order risk assessment” action that does the same thing, and your “Order risk analyzed” trigger will fire off it properly. Then open the run history on your cancel/hold workflow and confirm every step actually executed.
I really like this idea. The Bogus Gateway already simulates payment outcomes, so extending it to simulate different fraud risk levels feels like a natural next step.
Being able to generate a High Risk test order would make it much easier to validate Shopify Flow automations, especially for merchants who automatically hold, cancel, or tag suspicious orders. Right now, those workflows are difficult to test safely before going live.
This seems like a small enhancement that could significantly improve the developer experience and help merchants avoid costly mistakes in production.
This would be a genuinely useful enhancement. The Bogus Gateway already helps simulate different payment outcomes, so extending it to cover fraud scenarios feels like a natural next step.
Being able to generate a test High Risk order would let developers and merchants validate Shopify Flow automations, fraud handling, and fulfillment logic before deploying to production. That’s especially valuable for stores selling digital products or automatically fulfilling orders, where an untested workflow can lead to immediate losses. A dedicated test card (or another simple trigger) for a high-risk classification would make fraud testing mmuch more reliable without affecting real customer data. Hopefully the Shopify team considers adding this to improve the development and testing experience.
Thanks for the thoughtful response, really appreciate it.
You’re right that this fits naturally with what the Bogus Gateway already does. I’m aware there’s a workaround today using orderRiskAssessmentCreate or the “Create order risk assessment” action in Flow, but that still requires setting up an app with write_orders access or building an extra Flow step just to test something that should really be a one-click scenario during checkout itself.
A dedicated test card would remove that friction entirely, especially for developers who just want to do a quick manual QA pass without spinning up API calls or extra automation logic. It also lowers the barrier for less technical merchants who rely on Flow but aren’t comfortable working with GraphQL mutations directly.
Appreciate you taking the time to lay out the reasoning so clearly, hoping the Shopify team sees this thread and considers it for a future update.
You’re spot on about the fulfillment logic angle, that’s actually one of the strongest use cases here. For stores with automatic fulfillment, there’s currently a real gap: the only way to test a High Risk path today is either building an app with write_orders access to call orderRiskAssessmentCreate, or adding an extra step in Flow to manually inject the risk assessment. Neither is instant, and both require setup that a lot of smaller merchants or solo developers just won’t bother with, which means the untested-workflow risk you mentioned stays real in practice.
A dedicated test card would close that gap by making the whole thing checkout-native, no app, no extra Flow step, no API call. Just place the order and see the workflow react. That’s a meaningfully lower bar for testing, especially for teams that iterate fast and want to sanity-check fraud handling before every deploy.
Thanks, appreciate you laying out both paths clearly.
Yeah, I’m aware of the orderRiskAssessmentCreate route and the Flow action, and they definitely work as a workaround. My point with this suggestion was more about lowering the barrier for quick manual testing, not everyone wants to spin up an app with write_orders or add an extra Flow step just to sanity-check one workflow. A dedicated test card would just make it a one-step, checkout-native thing.
That said, good call on checking the run history for the cancel/hold workflow, that’s a solid way to confirm it’s actually firing end to end.
Exactly, that’s the core of it. There are existing workarounds through the API or Flow, but they add setup overhead that most developers won’t bother with for a quick sanity check. A dedicated test card would make it a one-step process, place the order, see the workflow react, no extra config needed.
Hoping enough people find this useful for the Shopify team to consider it.
(proposed)