@cartbase/storefront 0.1.2 → 0.2.0

package/src/cart-drawer/header.tsx

@@ -6,7 +6,7 @@ import { useCartDrawer } from "./context"
 /**
  * Cart drawer header — store title, item count badge, close button.
  *
- * Ported from `@1click/ui/src/cart-drawer/header.tsx` (v2.3.1). Barter
+ * Ported from `@1click/ui/src/cart-drawer/header.tsx` (v2.3.1). Cartbase
  * adjustment: the badge counts PRODUCT lines via the shared
  * `productItemCount` predicate (the source summed all lines) so a
  * backend-injected COD-fee line can never inflate the item count —

package/src/cart-drawer/item/index.tsx

@@ -15,13 +15,13 @@ import { CartItemVariant } from "./variant"
  * CartItem — a single cart line row: thumbnail, title, variant, quantity
  * stepper, price (with dual-currency + optional strikethrough), remove button.
  *
- * Ported from `@1click/ui/src/cart-drawer/item/index.tsx` (v2.3.1). Barter
+ * Ported from `@1click/ui/src/cart-drawer/item/index.tsx` (v2.3.1). Cartbase
  * data seam: `item` is the SDK's decorated `CartLineItem`
  * (`@cartbase/storefront/api/carts`) — per-line `total`/`original_total` are
  * server-computed EUR major units. Remove goes through the provider's
  * SDK-wired `removeItem` (DELETE line-items/:id, returns the full decorated
  * cart) instead of the Medusa server action. The variant row renders the
- * line's flat `variant_title` — barter cart lines carry the variant title
+ * line's flat `variant_title` — Cartbase cart lines carry the variant title
  * string, not an embedded variant object.
  *
  * `children` is rendered below the main row — intended for per-item upsell

package/src/cart-drawer/item/quantity.tsx

@@ -15,9 +15,9 @@ import { useCartDrawer } from "../context"
  * automatically (confirmed snapshot unchanged).
  *
  * Ported from `@1click/ui/src/cart-drawer/item/quantity.tsx` (v2.3.1).
- * Barter data seam: `updateQuantity` wraps
+ * Cartbase data seam: `updateQuantity` wraps
  * `POST /api/store/carts/:id/line-items/:lineId` with body `{quantity}` —
- * the barter contract accepts ONLY `quantity` (no metadata on update) and
+ * the Cartbase contract accepts ONLY `quantity` (no metadata on update) and
  * quantity 0 deletes the line (unreachable here: the stepper floor is 1;
  * removal is the dedicated remove button).
  */

package/src/cart-drawer/item/upsell.tsx

@@ -12,12 +12,12 @@ import { useCartDrawer } from "../context"
  * onAdd handler.
  *
  * Ported from `@1click/ui/src/cart-drawer/item/upsell.tsx` (v2.3.1).
- * Barter data seam: source stores fed this from Medusa product fetches —
+ * Cartbase data seam: source stores fed this from Medusa product fetches —
  * feed it from `@cartbase/storefront/api/search` `listRelatedProducts`
  * (per-anchor complements: manual admin picks + deterministic fallback)
  * mapped via `toCrossSellProduct` (`../cross-sell-sidebar`). `variantId`
  * was added to `UpsellProduct` and to the `onAdd` signature so the handler
- * can call the provider's `addItem(variantId)` directly — barter carts add
+ * can call the provider's `addItem(variantId)` directly — Cartbase carts add
  * by variant id, not product id. Prices are EUR major units.
  */
 
@@ -28,7 +28,7 @@ export type UpsellProduct = {
   thumbnail: string | null
   price: number
   currencyCode: string
-  /** Variant to add (barter add-to-cart is by variant id). */
+  /** Variant to add (Cartbase add-to-cart is by variant id). */
   variantId?: string
 }
 

package/src/cart-drawer/item/variant.tsx

@@ -5,8 +5,8 @@
  * under the product title in a cart line.
  *
  * Ported from `@1click/ui/src/cart-drawer/item/variant.tsx` (v2.3.1).
- * Barter data seam: the source rendered `variant.options[].value` from an
- * embedded Medusa variant object; barter cart lines carry the flat
+ * Cartbase data seam: the source rendered `variant.options[].value` from an
+ * embedded Medusa variant object; Cartbase cart lines carry the flat
  * `variant_title` string (SDK `CartLineItem.variant_title`) instead, so
  * that is the primary prop. Callers that fetched the full variant (PDP
  * context) can still pass structural `options` and get the original

package/src/cart-drawer/labels-bg.ts

@@ -6,7 +6,7 @@ import type { CartDrawerLabels } from "./labels"
  * Ships alongside the English defaults so Bulgarian stores get the
  * translated copy with a single import instead of hand-writing every
  * string. Strings match the originals from mindpages-storefront, plus the
- * barter summary-breakdown row additions.
+ * Cartbase summary-breakdown row additions.
  *
  * Usage in a store's layout:
  *

package/src/cart-drawer/labels.ts

@@ -6,7 +6,7 @@
  * `CartDrawerProvider`. English is the baseline; stores wanting Bulgarian,
  * German, etc. pass their own translations.
  *
- * Ported from `@1click/ui/src/cart-drawer/labels.ts` (v2.3.1). Barter
+ * Ported from `@1click/ui/src/cart-drawer/labels.ts` (v2.3.1). Cartbase
  * additions: the summary-breakdown row labels (`discount`, `tax`, `codFee`,
  * `giftCard`, `remainingToPay`) — the decorated cart carries
  * discount/tax/COD-fee/gift-card tender fields that the breakdown renders,
@@ -55,7 +55,7 @@ export type CartDrawerLabels = {
   secureCheckout: string
   shippingAndTaxCalculatedAtCheckout: string
 
-  // Summary breakdown rows (barter decorated-cart fields)
+  // Summary breakdown rows (Cartbase decorated-cart fields)
   discount: string
   tax: string
   /** Fallback only — the server's `cod_fee_label` wins when present. */

package/src/cart-drawer/summary-breakdown.tsx

@@ -12,8 +12,8 @@ import { useCartDrawer } from "./context"
  * pre-checkout context).
  *
  * Ported from `@1click/ui/src/cart-drawer/summary-breakdown.tsx` (v2.3.1)
- * and EXPANDED for barter: the source rendered a client-summed product
- * subtotal only; barter's decorated cart carries server-computed totals on
+ * and EXPANDED for Cartbase: the source rendered a client-summed product
+ * subtotal only; Cartbase's decorated cart carries server-computed totals on
  * every read (`subtotal`, `discount_total`, `shipping_total`, `tax_total`,
  * `cod_fee_total`/`cod_fee_label`, `gift_cards[]`, `gift_card_total`,
  * `gift_card_remainder`, `total` — all EUR major units), so this component

package/src/cart-drawer/template.tsx

@@ -29,7 +29,7 @@ import { isProductLine } from "../lib/cart-helpers"
  * body inside a `<CartDrawer>` shell. That way the store owns its
  * composition and still gets library updates to every primitive.
  *
- * Ported from `@1click/ui/src/cart-drawer/template.tsx` (v2.3.1). Barter
+ * Ported from `@1click/ui/src/cart-drawer/template.tsx` (v2.3.1). Cartbase
  * adaptations:
  * - Amounts are EUR major units — `rewards.pointsPerCurrency` is points
  *   per 1 EUR (the source's `/100` minor-unit division is gone), and
@@ -130,7 +130,7 @@ export function CartDrawerTemplate({
       .finally(() => setCrossSellLoaded(true))
   }, [hasItems, crossSellLoaded, config.crossSell?.loader])
 
-  // Cross-sell add → the provider's SDK addItem (barter adds by variant
+  // Cross-sell add → the provider's SDK addItem (Cartbase adds by variant
   // id). Cards built without a variantId no-op.
   const handleCrossSellAdd = useCallback(
     (_productId: string, variantId?: string) => {

package/src/cart-drawer/tiered-progress.tsx

@@ -11,7 +11,7 @@ import { useCartDrawer } from "./context"
  * originally extracted from mindpages-storefront
  * src/modules/cart-drawer/cart-tiered-progress.tsx.
  *
- * Barter money note: `cart.total` and tier `threshold`s are EUR decimal
+ * Cartbase money note: `cart.total` and tier `threshold`s are EUR decimal
  * major units (e.g. `{ threshold: 50 }` = €50) — configure tiers in major
  * units, not cents.
  */

package/src/checkout/address-error-copy.ts

@@ -3,7 +3,7 @@
  * checkout address surface.
  *
  * Ported from `@1click/ui/src/checkout/address-error-copy.ts` (v2.3.1) and
- * adapted to the barter error envelope: `StoreApiError` carries a structured
+ * adapted to the Cartbase error envelope: `StoreApiError` carries a structured
  * `code` (POST /api/store/carts/:id — docs/storefront/carts.md), so
  * translation is code-first; the substring patterns stay as the fallback for
  * network failures and any legacy wire.
@@ -20,7 +20,7 @@ const NETWORK_FALLBACK =
   "Няма връзка със сървъра. Моля, проверете интернет връзката и опитайте отново."
 
 /**
- * Barter cart-update error codes → BG copy (POST /api/store/carts/:id,
+ * Cartbase cart-update error codes → BG copy (POST /api/store/carts/:id,
  * docs/storefront/carts.md). Code-first, matched before any pattern.
  */
 export const ADDRESS_ERROR_CODE_COPY: Record<string, string> = {
@@ -76,7 +76,7 @@ const PATTERNS: Array<{ match: RegExp; copy: string }> = [
     copy: NETWORK_FALLBACK,
   },
   // The Next.js canned Server Components production message — surface a
-  // clean fallback instead of the English placeholder. (The barter SDK
+  // clean fallback instead of the English placeholder. (The Cartbase SDK
   // throws from the browser, so this only fires for stores that proxy the
   // save through a server action.)
   {

package/src/checkout/address-form.tsx

@@ -17,9 +17,9 @@ import { ErrorMessage } from "./error-message"
  * (`CheckoutClient` / `useCheckoutOrchestration`).
  *
  * Ported from `@1click/ui/src/checkout/address-form.tsx` (v2.3.1) with the
- * barter type seam only: `@medusajs/types` → the SDK's `CustomerAddress` /
+ * Cartbase type seam only: `@medusajs/types` → the SDK's `CustomerAddress` /
  * `CartAddress` partials. The `countries` list comes from the orchestration
- * hook's `regionCountries` — barter regions carry NO embedded countries
+ * hook's `regionCountries` — Cartbase regions carry NO embedded countries
  * array (api/regions.ts divergence), so the host supplies the list via the
  * hook's `countries` option (single-entry `countryCode` fallback).
  */

package/src/checkout/address-select.tsx

@@ -15,7 +15,7 @@ import { useCheckoutLabels } from "./context"
  * replace this one file locally.
  *
  * Ported from `@1click/ui/src/checkout/address-select.tsx` (v2.3.1) with
- * the barter type seam: `@medusajs/types` address DTOs → the SDK's
+ * the Cartbase type seam: `@medusajs/types` address DTOs → the SDK's
  * `CustomerAddress` (GET /api/store/customers/me — addresses embedded,
  * docs/storefront/customers.md) and `CartAddress` partials. Field names are
  * identical across both wires, so the compare/format logic is unchanged.

package/src/checkout/boxnow-locker-selector.tsx

@@ -17,11 +17,11 @@ import { useCheckoutLabels } from "./context"
  * BoxNowLockerSelector — full BoxNow locker picker for Bulgarian shipping.
  *
  * Ported from `@1click/ui/src/checkout/boxnow-locker-selector.tsx` (v2.3.1)
- * with the barter data seam: the locker directory comes from
+ * with the Cartbase data seam: the locker directory comes from
  * `listBoxNowLockers(client)` (`@cartbase/storefront/api/integrations`,
  * GET /api/store/integrations/boxnow/lockers — backend owns BoxNow API auth
  * + the 10-min cache; docs/storefront/integrations.md). The @1click data
- * helper returned `{ok, lockers}`; the barter SDK THROWS on 503 (not
+ * helper returned `{ok, lockers}`; the Cartbase SDK THROWS on 503 (not
  * configured) / 502 (carrier failure), so the fetch wrapper catches and
  * maps both to the same "temporarily unavailable" state. Availability
  * should be discovered via `carriers.boxnow.lockers_url` on the
@@ -38,7 +38,7 @@ import { useCheckoutLabels } from "./context"
  *  - title (not name)
  *  - addressLine1 / addressLine2 (not address.street/num)
  *  - postalCode (not address.city.name)
- *  - lat / lng on the root (numbers or null — the barter route coerces
+ *  - lat / lng on the root (numbers or null — the Cartbase route coerces
  *    malformed carrier coordinates to null, never NaN)
  *  - No isAPS / code / phones
  *

package/src/checkout/checkout-client.tsx

@@ -27,7 +27,7 @@ import {
  * automatically.
  *
  * Ported from `@1click/ui/src/checkout/checkout-client.tsx` (v2.3.1) with
- * the barter data seam:
+ * the Cartbase data seam:
  *
  *  - Takes the SDK `client` — every server call (address autosave,
  *    prepare-checkout, sync, complete, promo/gift-card apply, quantity
@@ -55,7 +55,7 @@ type CheckoutClientProps = {
   availableShippingMethods: StoreShippingOption[] | null
   availablePaymentMethods: PaymentProviderLike[] | null
   countryCode: string
-  /** Countries for the address form (barter regions embed none). */
+  /** Countries for the address form (Cartbase regions embed none). */
   countries?: Array<{ iso_2: string; display_name: string }>
   paymentMethodFilter?: (
     methods: PaymentProviderLike[] | null,

package/src/checkout/company-details.tsx

@@ -13,7 +13,7 @@ import { useCheckoutLabels } from "./context"
  * Ported from `@1click/ui/src/checkout/company-details.tsx` (v2.3.1)
  * unchanged — pure form UI; the values ride `formData` and the
  * orchestration hook persists them into `cart.metadata`
- * (company_name/company_vat/company_mol/company_address). Barter upgrade
+ * (company_name/company_vat/company_mol/company_address). Cartbase upgrade
  * over the @1click KNOWN_ISSUES state: the hook ALSO syncs
  * `company_name`/`company_eik` onto the signed-in customer profile
  * (PATCH /api/store/customers/me — first-class columns,

package/src/checkout/compare-addresses.ts

@@ -3,7 +3,7 @@
  * shipping-address fields. Returns true if every field matches.
  *
  * Ported from `@1click/ui/src/data/util/compare-addresses.ts` (v2.3.1)
- * unchanged. Lives in the checkout family because the barter SDK has no
+ * unchanged. Lives in the checkout family because the Cartbase SDK has no
  * data/util layer (the @1click data layer became `@cartbase/storefront/api`).
  * Extra file beyond the pre-declared export list → exported from the
  * family barrel only.

package/src/checkout/discount-section.tsx

@@ -15,16 +15,16 @@ import { translatePromotionError } from "./promotion-error-copy"
  * amount.
  *
  * Ported from `@1click/ui/src/checkout/discount-section.tsx` (v2.3.1) with
- * the barter data seam:
+ * the Cartbase data seam:
  *
  *  - `applyPromotions(codes)` (Medusa js-sdk server action, full-list
  *    replace) → `POST /api/store/carts/:id/promotions {promo_codes}` — the
- *    barter route is ADDITIVE (upserts each code's link, then re-applies),
+ *    Cartbase route is ADDITIVE (upserts each code's link, then re-applies),
  *    so only the NEW code is sent; already-applied codes stay put. The SDK
  *    carts module ships no wrapper for this route yet, so the component
  *    calls it through the client transport with the documented DTO
  *    (verified against src/app/api/store/carts/[id]/promotions/route.ts).
- *  - `cart.promotions` on the barter wire is the raw pivot embed
+ *  - `cart.promotions` on the Cartbase wire is the raw pivot embed
  *    (`[{promotion: {..., application_method}}]`) — unwrapped here, with a
  *    flat-row fallback should the decoration ever flatten it.
  *  - Errors are code-first (`promotion_not_found` / `promotion_inactive` /
@@ -46,7 +46,7 @@ type AppliedPromotion = {
   } | null
 }
 
-/** Unwrap the barter pivot embed; tolerate an already-flat row. */
+/** Unwrap the Cartbase pivot embed; tolerate an already-flat row. */
 function extractPromotions(cart: Cart): AppliedPromotion[] {
   const raw = (cart.promotions ?? []) as Array<Record<string, unknown>>
   return raw
@@ -84,7 +84,7 @@ export function DiscountSection({
     setLoading(true)
     setError("")
     try {
-      // Additive apply — the barter route upserts the new code's link and
+      // Additive apply — the Cartbase route upserts the new code's link and
       // re-applies every cart promotion; already-applied codes stay.
       const { cart: updated } = await applyPromotions(client, cart.id, [code.trim()])
       onCartChange?.(updated)

package/src/checkout/econt-office-selector.tsx

@@ -10,13 +10,13 @@ import { useCheckoutLabels } from "./context"
  * EcontOfficeSelector — full Econt office picker for Bulgarian shipping.
  *
  * Ported from `@1click/ui/src/checkout/econt-office-selector.tsx` (v2.3.1)
- * verbatim — this component has NO barter data seam: the office directory
+ * verbatim — this component has NO Cartbase data seam: the office directory
  * comes straight from Econt's public Nomenclatures endpoint (client-side,
  * cached globally per page load), and the CHOSEN office is handed to the
  * orchestration hook, which writes it into `carrier_metadata` exactly once
  * at Buy click (POST /api/store/carts/:id/prepare-checkout —
  * docs/storefront/checkout.md). The geocode helpers moved into the checkout
- * family (`./geocode`) because the barter lib family doesn't ship one.
+ * family (`./geocode`) because the Cartbase lib family doesn't ship one.
  *
  * Behavior:
  * - On mount, fetches the full Econt offices list from the public Econt

package/src/checkout/gift-card-section.tsx

@@ -15,8 +15,8 @@ import { translateGiftCardError } from "./payment-error-copy"
  * summary card, plus the applied-cards chip list (masked `last4`, per-card
  * coverage, remove).
  *
- * NEW in the barter port (no @1click equivalent — gift-card tender is a
- * barter feature, docs/storefront/gift-cards.md). Built in the
+ * NEW in the Cartbase port (no @1click equivalent — gift-card tender is a
+ * Cartbase feature, docs/storefront/gift-cards.md). Built in the
  * DiscountSection idiom so the two summary widgets read as one family.
  *
  * Contract discipline baked in:

package/src/checkout/labels-bg.ts

@@ -3,7 +3,7 @@ import type { CheckoutLabels } from "./labels"
 /**
  * Bulgarian translations for the checkout.
  *
- * Ported from `@1click/ui/src/checkout/labels-bg.ts` (v2.3.1) + the barter
+ * Ported from `@1click/ui/src/checkout/labels-bg.ts` (v2.3.1) + the Cartbase
  * gift-card keys. Strings match the originals from mindpages-storefront's
  * checkout-client monolith.
  *

package/src/checkout/labels.ts

@@ -2,8 +2,8 @@
  * Checkout labels — default English copy.
  *
  * Ported from `@1click/ui/src/checkout/labels.ts` (v2.3.1) with the
- * barter additions: gift-card tender labels (`giftCard*`) for the new
- * GiftCardSection (gift cards are a barter feature with no @1click
+ * Cartbase additions: gift-card tender labels (`giftCard*`) for the new
+ * GiftCardSection (gift cards are a Cartbase feature with no @1click
  * equivalent — docs/storefront/gift-cards.md).
  *
  * Every user-facing string in the checkout module comes from a
@@ -87,7 +87,7 @@ export type CheckoutLabels = {
   discountCode: string
   discountSub: string
   /** Default label for the cash-on-delivery fee row. Used as the third-
-   *  level fallback when neither the cart's `cod_fee_label` (barter
+   *  level fallback when neither the cart's `cod_fee_label` (Cartbase
    *  server truth) nor a per-store override is available. */
   codFee: string
   recommended: string
@@ -96,7 +96,7 @@ export type CheckoutLabels = {
   remove: string
   secureCheckout: string
 
-  // Gift cards (barter gift-card tender — docs/storefront/gift-cards.md)
+  // Gift cards (Cartbase gift-card tender — docs/storefront/gift-cards.md)
   giftCard: string
   giftCardSub: string
   giftCardPlaceholder: string

package/src/checkout/line-item-card.tsx

@@ -14,13 +14,13 @@ import { useCheckoutLabels } from "./context"
  * and dual-currency price.
  *
  * Ported from `@1click/ui/src/checkout/line-item-card.tsx` (v2.3.1) with
- * the barter data seam: the cookie-bound `updateLineItem` server action →
+ * the Cartbase data seam: the cookie-bound `updateLineItem` server action →
  * `carts.updateLineItem(client, cartId, lineId, {quantity})`
  * (POST /api/store/carts/:id/line-items/:lineId — docs/storefront/
  * carts.md). The route returns the freshly decorated cart; pass
  * `onCartChange` so the host can update its cart state (or
  * `router.refresh()` in an RSC app). `variant.title` → the flat
- * `variant_title` column of the barter line DTO.
+ * `variant_title` column of the Cartbase line DTO.
  *
  * Checkout is master-level: customers cannot remove items here.
  * Removal lives in the cart drawer only.

package/src/checkout/order-summary.tsx

@@ -17,15 +17,15 @@ import { GiftCardSection } from "./gift-card-section"
  * tax / total, optional optimistic overrides used during method selection.
  *
  * Ported from `@1click/ui/src/checkout/order-summary.tsx` (v2.3.1) with
- * the barter data seam:
+ * the Cartbase data seam:
  *
- *  - COD fee is CART-LEVEL decoration on the barter wire —
+ *  - COD fee is CART-LEVEL decoration on the Cartbase wire —
  *    `cart.cod_fee_total` / `cart.cod_fee_label`, folded into `cart.total`
  *    while a live pp_cod session exists (docs/storefront/checkout.md) —
  *    NOT a metadata-flagged fee line item. The fee row + optimistic math
  *    read those fields; `isProductLine` is kept as a defensive filter for
  *    any legacy fee-line carts.
- *  - Gift-card tender rows (barter feature): `gift_card_total` renders as
+ *  - Gift-card tender rows (Cartbase feature): `gift_card_total` renders as
  *    a negative tender row and `gift_card_remainder` as "Remaining to pay"
  *    UNDER the (unchanged) total — tender never moves totals
  *    (docs/storefront/gift-cards.md). `GiftCardSection` mounts next to
@@ -254,7 +254,7 @@ export function OrderSummary({
 }: OrderSummaryProps) {
   const labels = useCheckoutLabels()
 
-  // Product rows only. Barter's COD fee is cart-level decoration (never a
+  // Product rows only. Cartbase's COD fee is cart-level decoration (never a
   // line item), so this filter is defensive — it also hides any
   // metadata-flagged fee line a legacy/ported cart might still carry.
   const allItems = cart.items ?? []
@@ -269,7 +269,7 @@ export function OrderSummary({
   const shippingKnown = shippingCost !== null && shippingCost !== undefined
 
   // Effective COD fee: optimistic prediction wins until the cart catches
-  // up. Three states (null / 0 / positive). Barter server truth is
+  // up. Three states (null / 0 / positive). Cartbase server truth is
   // `cart.cod_fee_total` (folded into cart.total while a pp_cod session
   // lives — docs/storefront/checkout.md).
   const realCodFeeAmount = cart.cod_fee_total ?? 0
@@ -296,7 +296,7 @@ export function OrderSummary({
     realCodFeeAmount,
   ])
 
-  // Subtotal: barter's `item_total` is products-only (the COD fee is not a
+  // Subtotal: Cartbase's `item_total` is products-only (the COD fee is not a
   // line item), so no fee subtraction is needed — direct server truth.
   const productSubtotal = cart.item_total ?? 0
 
@@ -318,7 +318,7 @@ export function OrderSummary({
   }, [cart.shipping_total, optimisticShippingCost, onOptimisticShippingClear])
 
   // Clear optimistic COD fee once the cart's decoration matches the
-  // prediction (barter: cod_fee_total, not a fee line item).
+  // prediction (Cartbase: cod_fee_total, not a fee line item).
   useEffect(() => {
     if (optimisticCodFee === null || optimisticCodFee === undefined) return
     const synced = realCodFeeAmount === optimisticCodFee

package/src/checkout/payment-button.tsx

@@ -18,10 +18,10 @@ const PROCESSING_MESSAGE_INTERVAL_MS = 1800
  * PaymentButton — top-level "place order" button.
  *
  * Ported from `@1click/ui/src/checkout/payment-button.tsx` (v2.3.1) with
- * the barter data seam: the `cart` prop is structural (only `id`, `total`,
- * `currency_code` are read — any decorated barter cart satisfies it), and
+ * the Cartbase data seam: the `cart` prop is structural (only `id`, `total`,
+ * `currency_code` are read — any decorated Cartbase cart satisfies it), and
  * the `logCheckoutError` Supabase writer becomes the optional `logError`
- * callback (barter has no store-side log endpoint; every production log
+ * callback (Cartbase has no store-side log endpoint; every production log
  * point is preserved through the callback).
  *
  * The button delegates entirely to the orchestration hook's
@@ -270,7 +270,7 @@ export function PaymentButton({
       setSubmitting(false)
     } catch (err: unknown) {
       // Next.js's `redirect()` throws a NEXT_REDIRECT error — that is
-      // success, not failure. The barter default path navigates via
+      // success, not failure. The Cartbase default path navigates via
       // window.location.assign (no throw), but a store routing
       // `onOrderPlaced` through a server action still hits this; don't
       // translate it — let it propagate so the navigation happens.

package/src/checkout/payment-error-copy.ts

@@ -3,11 +3,11 @@
  * Bulgarian copy for the checkout payment surface.
  *
  * Ported from `@1click/ui/src/checkout/payment-error-copy.ts` (v2.3.1) and
- * adapted to the barter error envelope: the store API throws `StoreApiError`
+ * adapted to the Cartbase error envelope: the store API throws `StoreApiError`
  * with a STRUCTURED `code` (docs/storefront/checkout.md lists every code per
  * endpoint), so translation is **code-first** — the substring patterns from
  * the Medusa era are kept as the fallback layer for Stripe.js browser errors
- * (which have no barter code) and any legacy wire.
+ * (which have no Cartbase code) and any legacy wire.
  *
  * Why this exists: Stripe and API errors are technical English strings
  * ("Your card's security code is incorrect.", "fetch failed"). Showing them
@@ -26,7 +26,7 @@ const GENERIC_COD =
   "Поръчката не може да бъде финализирана в момента. Моля, опитайте отново след малко."
 
 /**
- * Barter store-API error codes → BG copy. Covers EVERY code documented for
+ * Cartbase store-API error codes → BG copy. Covers EVERY code documented for
  * POST /api/store/carts/:id/complete, prepare-checkout,
  * sync-payment-amount and refresh-payment-if-terminal
  * (docs/storefront/checkout.md + carts.completeCart JSDoc). Code-first:
@@ -110,7 +110,7 @@ const GIFT_CARD_GENERIC =
  * Map of Stripe error codes / decline codes / common substrings to BG copy.
  * Substring match is case-insensitive. First match wins, so order from
  * most-specific to most-generic. Kept verbatim from the production port —
- * Stripe.js browser errors carry no barter `code`, so this layer still does
+ * Stripe.js browser errors carry no Cartbase `code`, so this layer still does
  * the heavy lifting on the card path.
  *
  * Stripe error code reference:
@@ -203,7 +203,7 @@ const API_PATTERNS: Array<{ match: RegExp; copy: string }> = [
   },
 ]
 
-/** Pull the structured barter error code out of any thrown value. */
+/** Pull the structured Cartbase error code out of any thrown value. */
 function extractCode(err: unknown): string | null {
   if (err && typeof err === "object") {
     const code = (err as { code?: unknown }).code
@@ -214,7 +214,7 @@ function extractCode(err: unknown): string | null {
 
 /**
  * Translate any thrown / returned error into customer-facing Bulgarian.
- * Code-first (barter `StoreApiError.code`), then Stripe substring patterns,
+ * Code-first (Cartbase `StoreApiError.code`), then Stripe substring patterns,
  * then legacy API substrings, then the per-context generic.
  *
  * @param err - the error from a try/catch or a Stripe error response

package/src/checkout/payment-method-list.tsx

@@ -19,9 +19,9 @@ import type { CheckoutLogError } from "./use-checkout-orchestration"
  * per-method code here.
  *
  * Ported from `@1click/ui/src/checkout/payment-method-list.tsx` (v2.3.1)
- * with the barter data seam: the `cart` prop is structural, and the
+ * with the Cartbase data seam: the `cart` prop is structural, and the
  * `logCheckoutError` Supabase writer becomes the optional `logError`
- * callback. Provider semantics on the barter wire: the "card" tab is
+ * callback. Provider semantics on the Cartbase wire: the "card" tab is
  * `pp_stripe`, the "cod" tab is `pp_cod` (native fee via the integrations
  * `cod` block) or `pp_manual` (offline, no fee) — the orchestration hook
  * resolves the ids (`hasCard`/`hasCod`/`cardId`/`codId`); both listings

package/src/checkout/payment-wrapper.tsx

@@ -10,11 +10,11 @@ import { StripeScopeProvider } from "./stripe-wrapper"
  * PaymentWrapper — provides Stripe Elements scope context to descendants.
  *
  * Ported from `@1click/ui/src/checkout/payment-wrapper.tsx` (v2.3.1).
- * Barter adaptations: the `cart` prop is the barter `Cart` DTO (only
+ * Cartbase adaptations: the `cart` prop is the Cartbase `Cart` DTO (only
  * `currency_code` is read — typed structurally so any decorated cart
- * satisfies it); env var naming gains `NEXT_PUBLIC_STRIPE_KEY` as the
- * canonical name, with the Medusa-era fallbacks kept so ported storefronts
- * keep working unchanged.
+ * satisfies it); `NEXT_PUBLIC_STRIPE_KEY` is the canonical env name
+ * (the Medusa-era fallback was dropped 2026-08-04, before any external
+ * consumer existed).
  *
  * As of the deferred-checkout architecture, this wrapper supplies an
  * optimistic `amount` + `currency` (computed by the orchestration hook)
@@ -30,16 +30,13 @@ import { StripeScopeProvider } from "./stripe-wrapper"
  *   </PaymentWrapper>
  *
  * Environment variables (read at module load time):
- *   - NEXT_PUBLIC_STRIPE_KEY  OR
- *     NEXT_PUBLIC_MEDUSA_PAYMENTS_PUBLISHABLE_KEY (legacy fallback)
- *   - NEXT_PUBLIC_MEDUSA_PAYMENTS_ACCOUNT_ID (optional, connect accounts)
+ *   - NEXT_PUBLIC_STRIPE_KEY
+ *   - NEXT_PUBLIC_STRIPE_ACCOUNT_ID (optional, connect accounts)
  */
 
-const stripeKey =
-  process.env.NEXT_PUBLIC_STRIPE_KEY ||
-  process.env.NEXT_PUBLIC_MEDUSA_PAYMENTS_PUBLISHABLE_KEY
+const stripeKey = process.env.NEXT_PUBLIC_STRIPE_KEY
 
-const stripeAccountId = process.env.NEXT_PUBLIC_MEDUSA_PAYMENTS_ACCOUNT_ID
+const stripeAccountId = process.env.NEXT_PUBLIC_STRIPE_ACCOUNT_ID
 
 const stripePromise = stripeKey
   ? loadStripe(

package/src/checkout/promotion-error-copy.ts

@@ -3,7 +3,7 @@
  * checkout discount-code surface.
  *
  * Ported from `@1click/ui/src/checkout/promotion-error-copy.ts` (v2.3.1)
- * and adapted to the barter error envelope: the cart-promotions route
+ * and adapted to the Cartbase error envelope: the cart-promotions route
  * (POST /api/store/carts/:id/promotions) throws structured codes —
  * `promotion_not_found`, `promotion_inactive`, `promotion_misconfigured`,
  * `promotion_unsupported_type`, plus the cart-level `cart_not_found` /
@@ -34,7 +34,7 @@ const EXHAUSTED =
   "Промоцията е изчерпана и вече не може да бъде използвана."
 
 /**
- * Barter promotion error codes → BG copy (POST/DELETE
+ * Cartbase promotion error codes → BG copy (POST/DELETE
  * /api/store/carts/:id/promotions + src/lib/promotions/apply.ts).
  */
 export const PROMOTION_ERROR_CODE_COPY: Record<string, string> = {

package/src/checkout/shipping-method-list.tsx

@@ -19,7 +19,7 @@ import { ErrorMessage } from "./error-message"
  * matching picker expands inline inside that row.
  *
  * Ported from `@1click/ui/src/checkout/shipping-method-list.tsx` (v2.3.1)
- * with the barter data seam: options are `StoreShippingOption` rows from
+ * with the Cartbase data seam: options are `StoreShippingOption` rows from
  * `checkout.listShippingOptions(client, {cart_id})` — rule-filtered and
  * display-ordered SERVER-SIDE (checkout rules + `checkout_method_order`,
  * docs/storefront/checkout.md); this component only renders what arrives.
@@ -183,7 +183,7 @@ export function CheckoutShippingMethodList({
             // mid-courier-switch — the in-flight switch would otherwise
             // leave a brief window where prices are calculated=true but
             // the new option's price hasn't landed in the map yet,
-            // making it look broken. (Barter serves flat prices today;
+            // making it look broken. (Cartbase serves flat prices today;
             // the calculated branch is forward-compat —
             // docs/storefront/checkout.md.)
             const cantCalc =

package/src/checkout/stripe-wrapper.tsx

@@ -18,7 +18,7 @@ import {
  *
  * Ported from `@1click/ui/src/checkout/stripe-wrapper.tsx` (v2.3.1)
  * unchanged — no data seam; the PaymentIntent seam moved server-side into
- * barter's POST /api/store/carts/:id/prepare-checkout.
+ * Cartbase's POST /api/store/carts/:id/prepare-checkout.
  *
  * `<Elements>` is mounted with `mode: 'payment'`, `amount`, `currency` — NO
  * PaymentIntent exists on the backend yet. The PI is minted at Buy click by