This step type no longer exists
A checkout_flow Logic Block step (and the named "checkout flow" config it pointed at) previously let an org admin put gating logic — a promo code, a plan-downgrade rule — in front of a payment checkout. That mechanism was retired along with named checkout flows. It has not been replaced yet.
Today, a payment connector's checkout action resolves its Product Catalog label (see Setting up a payment connector) only on the direct POST /app/{orgcode}/ipaas/{connector} route (action selected by the action_id body field, not a URL segment). Calling the same action from inside a Logic Block's generic connector step, or from an automation's event destination, does not resolve the label — it would need the provider's raw price/product/plan id passed in directly, which defeats the point of the Product Catalog.
In practice: if you need eligibility logic in front of checkout, run that logic in your own client/backend first, then call the direct checkout route only once you've decided the purchase is allowed. There's currently no supported way to make that decision *inside* nostackai and still have it resolve a Product Catalog label for you.
Planned
Gating a payment-connector checkout behind Logic Block conditions, with label resolution intact, is a known gap and on the roadmap. This page will be updated once it's supported.