My Marketplaces

/my-marketplaces — MyMarketplacesPageModule. Gated by the MY_MARKETPLACES permission, which every authenticated supplier holds by default.

This is where a supplier sees which sales channels Payability can read, and fixes them when a connection breaks. Since advances are underwritten against marketplace receipts, a broken connection has direct financial consequences.

Components

my-marketplaces-page/

The page shell and layout.

marketplace-widget/

One connected channel — logo, name, connection status, actions.

marketplace-content/

Expanded detail panel for a channel.

add-marketplaces/

The add-a-channel flow.

unsuported-marketplaces/

Report a channel Payability does not integrate with.

marketplace-placeholder/

Loading skeleton for the grid.

marketplace-single-placeholder/

Loading skeleton for one channel.

State

Two entity slices back the page:

marketplaces

The catalog of supported channels. Persisted to localStorage (marketplaces_storage), so the page renders instantly on repeat visits.

supplierMarketplaces

This supplier’s connections and their health.

Both are keyed by marketplaceKey. See Entity Slices.

Adding a channel

add-marketplaces
  → pick from the catalog (marketplaces slice)
  → dispatch addSupplierMarketplace | bulkAddSupplierMarketplaces
  → per-channel compliance steps (see Marketplaces & Compliance)
  → dispatch saveSupplierMarketplace

Channels Payability does not support are recorded through bulkAddUnsupportedSupplierMarketplaces — they never produce a connector, but they give underwriting a complete picture of the supplier’s revenue.

Connection status

Each connection carries a status expressed through several enums at different granularities:

MpPermissionEnum

The supplier’s authorization on the channel — approved, verified, pending, rejected, incomplete, disabled, sales resolution, and their perm- variants.

ApiStatus

The API connection itself — needed, required, rejected, confirmed, incomplete, in-review, pending.

AccessStatusEnum

The compliance record — pending, incomplete, rejected, completed, verified.

Status is rendered with status-badge and status-chip.

Reconnection

Amazon and Shopify connections are monitored continuously by the API connectors, which raise a banner and offer a guided reconnect modal when a connection drops. See Marketplace API Connectors.

Relevant user fields:

status.ascApiStatus

Amazon Seller Central API connection status.

user.amazonApiSwitching

The supplier is mid-migration between Amazon connection methods.

Amazon flows

Dispatched through the marketplaces slice:

openAmazonInviteWrapper

The invite-Payability wizard. Also launched from the suspension modal when Amazon access has been diverted.

openAmazonPermissionWrapper

The grant-permissions wizard.

amazonSuspendedProcessBreak / amazonSuspendedProcessCompleted

Outcomes of the Amazon-suspended flow (modals/amazon-suspended/).

modals/add-selling-info-modal/ collects marketplace credentials where a manual connection is required.

Cancellation interaction

CancellationBannerInitializerService reads fundingParticulars.lastOptOutDate from each supplier marketplace to build the cancellation banners — so this slice also drives cancellation messaging. See Cancellation & Reactivation.

Analytics

Two families of events cover this page and the onboarding equivalent:

MarketplaceEventType

Lifecycle — Marketplace_Access_Completed, Marketplace_Access_Updated, marketplace_deleted, Removed_Marketplace, new_marketplace_added.

LinkMarketplaceEventType

The onboarding link wizard — show more/less, per-marketplace connect clicks, Submitted Marketplace, Completed_ChooseMarketplace, Added Additional Marketplace.

InviteMarketplaceEventType

The invite-Payability wizard.

Emitted by MarketplaceEventsService and AmazonEventTrackerService. Full list: Event Catalog.