The plugin's commerce client now always constructs in-process — there is no remaining HTTP mode. The in-process client currently wires only the x402 payment gateway, not Stripe.
As a result, createOrderFromCart's success path is unreachable for Stripe-based checkout when running in-process, since there's no way to complete a Stripe payment confirmation against the in-process gateway wiring.
The corresponding test coverage was parked as test.todo in the checkout sandbox test suite (storefront-checkout.sandbox.test.ts) pending the Stripe gateway being wired in-process. The parked cases cover:
- idempotency-key forwarding
buyerRef / clientAction / ship-to passthrough- private-field stripping
- replay /
alreadyPlaced handling
- total formatting, including locale
- typed error-code mapping
Once the Stripe gateway is wired into the in-process commerce client, these test.todo cases should be converted to real assertions.
The plugin's commerce client now always constructs in-process — there is no remaining HTTP mode. The in-process client currently wires only the x402 payment gateway, not Stripe.
As a result,
createOrderFromCart's success path is unreachable for Stripe-based checkout when running in-process, since there's no way to complete a Stripe payment confirmation against the in-process gateway wiring.The corresponding test coverage was parked as
test.todoin the checkout sandbox test suite (storefront-checkout.sandbox.test.ts) pending the Stripe gateway being wired in-process. The parked cases cover:buyerRef/clientAction/ ship-to passthroughalreadyPlacedhandlingOnce the Stripe gateway is wired into the in-process commerce client, these
test.todocases should be converted to real assertions.