Checkout Workflow Bypass

Checkout Workflow Bypass

Skip the payment step, ship the order anyway.

What Is Checkout Workflow Bypass?

A checkout splits into a payment step and a confirm step, and the server trusts the browser to call them in that order. That makes it an insecure-design flaw, a missing invariant rather than a coding slip. You'll capture the payment request, change its path to the confirm step, and watch an order release to the warehouse with nothing paid. Then you enforce the order state machine on the server so an order reaches confirmed only from a paid state that the payment provider set.

What You'll Learn in Checkout Workflow Bypass

Checkout Workflow Bypass — Training Steps

  1. Reach the payment step

    Halvenroot's checkout takes an order to a payment step, then a confirm step that releases it to the warehouse. Bob has a full basket, order HR-58213, sitting at the payment step. He opens it to see how the two steps talk to the server before he pays for anything.

  2. Two steps, in order

    The progress rail is the whole design, and the whole weakness.

  3. Capture the payment request

    Bob clicks Continue to payment, but he is not here to pay. He just wants the request the browser sends, captured in the Network panel so he can work on it.

  4. The request Bob will tamper

    The captured request is the first of the two steps.

  5. Skip to confirm

    Bob edits the captured request in the Network panel, changing the path from the payment step to the confirm step, and resends it. No card, no payment provider, just the second step called directly.

  6. Confirmed, nothing paid

    The server took the confirm step on his word. The order is released to the warehouse, and the amount paid is zero.

  7. The order ledger

    Bob opens his orders to see the result land where it counts.

  8. Released for free

    The $1,247.40 basket is now a confirmed order heading to dispatch.

  9. Knowledge check

  10. The finance alert

    You own Halvenroot's checkout service. Overnight, finance flagged an order that shipped with nothing paid against it. Security operations has traced how and emailed you.

Security Framework Coverage

OWASP Top 10

  • A06:2025 Insecure Design
  • A04:2021 Insecure Design

OWASP ASVS

  • V2.3.1 Business Logic Security

CWE

  • CWE-841 Improper Enforcement of Behavioral Workflow
  • CWE-840 Business Logic Errors

CIS Controls

  • CIS 16 Application Software Security

NIST CSF

  • PR.AT-02 Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind
  • PR.PS Platform Security

NICE Framework

  • DD-WRL-003 Secure Software Development