Merchant-side, the scope that matters most is read-only lookup_invoice — matching incoming zaps to orders is the real reconciliation work, and full pay access just to close that loop is a trust leap most of us don't want to take. Curious if the blocker is the NWC spec itself or Strike's API surface.