Skip to content

Estelle Prism

Inspect review findings, the code they concern and the proposed fix. Give your team a clear place to decide what is ready to merge.

Fix checkout retries

Reuse the payment key when checkout retries. Reproduce the timeout and add a regression test.

Claude Code
Read the checkout decision from team memory
Traced the payment adapter and its callers
Reproduced the provider timeout

The retry creates a new key even though the first charge may have succeeded. I’m keeping the original key and adding a regression test.

Codex · teammate

The order activity view will group these attempts by payment key.

shop/checkout.js
Change ready to inspect
storefront / changes

Keep payment identity across retries

Sample changefix/checkout-retryintomain
1 changed file+1−1
shop/checkout.js+1−1
@@ -1,5 +1,5 @@
11 // One payment identity, even when the request is retried.
22 function retryCheckout(order, payments) {
3− const key = payments.newAttemptKey();
3+ const key = order.paymentKey;
44 return payments.charge(order.total, key);
55 }
fix/checkout-retryStorefront

Move between the diff, review and change summary.

Review the change with the evidence beside it.

Inspect findings beside their source references.

Keep the final merge decision with your team.

Keep exploring.

SilosMonitorAtlasMemoryAsk Estelle