On the web, with more detail: Keep sites apart.

Mishka Pay is built for one install that serves many sites, as Mishka CMS does. Inside Mishka CMS the core starts mishka_installer's registry before any extension, and Mishka Pay's application starts its providers itself (listed in its plugins/0, as every CMS package does), so an extension that uses it lists only its own plugins: its keys plugin, listeners and broadcast.

An extension with Mishka Pay resources lists, in its application's plugins/0 and children, MishkaPay.Ash.listeners(MyExtension.Pay) (each resource's <Resource>.MishkaPayListener), and adds mishka_pay_inbox to Oban's queues; AshOban refuses to start without that queue. In its tests, MishkaPay.Test.setup!() and MishkaPay.Test.await_plugin!(MishkaPay.Providers.Stripe) in test_helper.exs give the keys table and wait for Stripe to register.

  1. Keys per site. The keys plugin answers each site's own keys and settings (refunds once or many, merchant of record, Stripe Tax) from its database, at runtime. Changing a site's keys needs no restart.

  2. Every call names the site. tenant: site.id on every call (MishkaPay.checkout/1, MishkaPay.fetch_payment/3...).

  3. Webhooks per site. Each site's Stripe endpoint is /pay/webhooks/stripe/<site id>; the signature is checked with that site's webhook_secret, and the event carries the site.

  4. Ash multitenancy. Your Mishka Pay resources may use Ash multitenancy on your own attribute:

    multitenancy do
      strategy :attribute
      attribute :site_id
    end

    Actions then run with tenant: site.id, the provider's keys are read for that site, and each webhook's row is synced inside the site its URL names. The same Stripe object in two sites is two rows. Keep the inbox global: a webhook arrives before any site is chosen.

    Without Ash multitenancy, name your own column instead, and each create action writes the site there too:

    mishka_pay do
      kind :payment
      tenant_from :site_id
    end
    
    relationships do
      belongs_to :site, MyApp.Sites.Site
    end
  5. Real time per site. MishkaPay.PubSub broadcasts on each site's own topic; subscribe a site's admin to MishkaPay.PubSub.topic(:payment, site.id).