Skip to main content

Platform Boundaries

eshopOS coordinates commerce operations, but it does not replace every external provider or professional responsibility around a merchant's business.

eshopOS Is Not​

eshopOS is not:

  • a bank
  • a payment processor
  • a card network
  • a shipping carrier
  • a tax authority
  • a legal, accounting, or financial adviser
  • a marketplace operator for third-party marketplaces
  • a provider of external courier credentials
  • a guarantee that an external provider will approve, settle, deliver, or accept a transaction

Merchant Responsibilities​

Merchants remain responsible for:

  • accurate product, pricing, stock, and tax setup
  • choosing and maintaining payment provider accounts
  • choosing and maintaining shipping or courier provider accounts
  • complying with local tax, consumer protection, privacy, and sector rules
  • protecting account credentials and staff access
  • validating live checkout, fulfillment, and notification behavior before relying on it

Developer Responsibilities​

Developers remain responsible for:

  • keeping secret keys and provider tokens server-side
  • validating webhook signatures where available
  • using idempotency keys for retryable writes
  • keeping test and live integrations separate
  • handling customer data only for approved merchant purposes
  • following documented public API and dashboard flows

Provider Responsibilities​

External providers remain responsible for their own service availability, approval decisions, settlement behavior, carrier delivery, API changes, and support obligations.

When eshopOS connects to a provider, it helps the merchant operate through that connection. It does not take over the provider's obligations.