Hold for Review

Championed a Shopify workflow for reviewing potentially risky orders while keeping automatic capture available for routine payments.

My role

Senior Software Engineer

  • Payments
  • Risk
  • Fulfillment

The problem

A merchant who wants to review a particular order should still be able to capture routine payments automatically. To make that possible, a review decision has to stay consistent across payment authorization, capture, and fulfillment, even when payment methods support different capture behavior.

My contributions

  • I championed the workflow and integrated merchant-defined review decisions into payment and order handling.
  • I implemented parts of the hold and release behavior, accounting for differences in payment capture and keeping the review decision consistent when lifecycle events were retried.
  • I contributed to order visibility, review controls, settings, and notifications in the merchant admin. I also took part in live testing of the end-to-end workflow.

Decisions and trade-offs

Reuse the payment flow when a hold is released

Releasing an order for fulfillment can affect payment handling. An authorization and a capture are different states, and methods vary in whether they support a separate capture. The workflow had to respect the payment’s current state when a merchant released the hold or a lifecycle event was retried.

We reconsidered the design when the review workflow started to need its own recovery logic. The established payment flows already handled much of that lifecycle. We reused them and kept the new logic focused on applying and releasing the hold. That left fewer payment recovery paths to maintain and validate.

Make the next action clear

A hold only helps if a merchant can find the order, understand why it is waiting, and see what they can do next. That was the purpose of the order visibility and review controls I contributed to. In live testing, we followed an order from the review decision through the merchant’s view of the hold, then checked payment and fulfillment after release.

Outcome

  • Implemented the review workflow and validated it end to end in live testing.Team delivery

What I took away. Start with the merchant decision, then trace it through each system it changes. Reusing established payment behavior reduced the number of custom recovery paths to maintain and test.

Tools and systems

  • Payments lifecycle
  • Distributed systems
  • End-to-end validation

Further reading