apps/web/lib/api/links/usage-checks.ts (1)

20-23: Enterprise exemption is correct; consider centralizing plan checks.

LGTM on not throwing for enterprise. To avoid drift across files, consider a shared helper like isEnterprisePlan(plan) (or enum) and reuse it here and in routes/UI.

packages/email/src/templates/links-limit.tsx (1)

83-94: Fix copy: missing “to” (twice).

Reads awkwardly: “upgrade the … plan add more links.” Suggest:

-                All your existing links will continue to work, and we are still
-                collecting data on them, but you'll need to upgrade the{" "}
+                All your existing links will continue to work, and we are still
+                collecting data on them, but you'll need to upgrade to the{" "}
...
-                </Link>{" "}
-                add more links.
+                </Link>{" "}
+                to add more links.

apps/web/lib/actions/partners/confirm-payouts.ts (2)

62-66: Use a shared constant for the $10 minimum and reuse the message.

Hardcoding 1000 and the string here will drift from UI. Define a single source of truth and reference it.

-    if (amount < 1000) {
-      throw new Error(
-        "Your payout total is less than the minimum invoice amount of $10.",
-      );
-    }
+    if (amount < MIN_PAYOUT_CENTS) {
+      throw new Error(MIN_PAYOUT_ERROR);
+    }

Outside this hunk, add:

// top-level (shared location preferred, e.g., lib/partners/constants)
export const MIN_PAYOUT_CENTS = 1_000 as const;
export const MIN_PAYOUT_ERROR = `Your payout total is less than the minimum invoice amount of $${MIN_PAYOUT_CENTS / 100}.`;

---

14-22: Tighten schema: enforce integer, nonnegative cents.

Prevents negative or float values slipping in.

-  amount: z.number(),
-  fee: z.number(),
-  total: z.number(),
+  amount: z.number().int().nonnegative(),
+  fee: z.number().int().nonnegative(),
+  total: z.number().int().nonnegative(),

apps/web/ui/partners/payout-invoice-sheet.tsx (2)

503-505: Good: tooltip explains the $10 minimum. Also block the button for < $10.

Currently the button isn’t disabled when 0 < amount < $10; ConfirmPayoutsButton suppresses hold on disabledTooltip, but also set disabled for clarity. Reuse a shared constant.

-          disabled={
-            eligiblePayoutsLoading || !selectedPaymentMethod || amount === 0
-          }
+          disabled={
+            eligiblePayoutsLoading ||
+            !selectedPaymentMethod ||
+            amount === 0 ||
+            (amount !== undefined && amount < MIN_PAYOUT_CENTS)
+          }
...
-            ) : amount && amount < 1000 ? (
-              "Your payout total is less than the minimum invoice amount of $10."
+            ) : amount && amount < MIN_PAYOUT_CENTS ? (
+              MIN_PAYOUT_ERROR
             ) : (

Add near the top (or import from a shared constants module used by the server action):

const MIN_PAYOUT_CENTS = 1_000;
const MIN_PAYOUT_ERROR = `Your payout total is less than the minimum invoice amount of $${MIN_PAYOUT_CENTS / 100}.`;

---

135-169: Stale memo deps: include payoutFee/paymentMethodsLoading; drop plan.

finalPaymentMethods depends on payoutFee, not plan. invoiceData uses paymentMethodsLoading in render but it’s not a dep, risking a stale skeleton.

-  const finalPaymentMethods = useMemo(
+  const finalPaymentMethods = useMemo(
     () =>
       paymentMethods?.map((pm) => {
         const paymentMethod = PAYMENT_METHODS[pm.type];
         const base = {
           ...paymentMethod,
           id: pm.id,
           fee: calculatePayoutFeeForMethod({
             paymentMethod: pm.type,
             payoutFee,
           }),
         };
         ...
       }),
-    [paymentMethods, plan],
+    [paymentMethods, payoutFee],
   );

-  }, [amount, paymentMethods, selectedPaymentMethod, cutoffPeriod]);
+  }, [amount, paymentMethods, paymentMethodsLoading, selectedPaymentMethod, cutoffPeriod]);

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Learnt from: devkiran
PR: dubinc/dub#2177
File: apps/web/lib/api/links/bulk-create-links.ts:66-84
Timestamp: 2025-06-06T07:59:03.120Z
Learning: In apps/web/lib/api/links/bulk-create-links.ts, the team accepts the risk of potential undefined results from links.find() operations when building invalidLinks arrays, because existing links are fetched from the database based on the input links, so matches are expected to always exist.