Why there is no Elvoric gateway
Elvoric is the utility and stays out of the money path, by rule and in code: no Elvoric account ever receives your client's money, no Elvoric code computes a commission, no card number or bank credential ever enters an Elvoric process, and every payment surface names the payee and says Elvoric is not a party to the payment. So the order is emitted by the platform and handed to a rail you chose — yours, or one an author wrote — and the money lands in your account, or your client's.
What you keep
You set the price and you keep 100% of it: a one-time licence, a per-store monthly, a setup fee, or your own commission collected through your own provider — Elvoric collects none of it, invoices nobody and files no VAT. You keep the customer relationship, which is the thing the big marketplaces take. You get distribution to Elvoric's makers at no acquisition cost, and the manifest is small enough to ship in a day for a pack and about a week for a connector.
What the runtime gives you
A manifest in plain JSON, plus the parts that make a plugin safe to install: scopes granted one at a time with a sentence your installer reads, denied by default; a per-store vault that is write-only — the key goes in once, a fingerprint comes out, and no read-back path exists for anyone; test mode first, so a connector cannot be activated on live keys until it has answered from the provider's own sandbox in the store's account; timeouts, a response cap and a circuit breaker, with the order falling back to WhatsApp or the bank block rather than breaking a shop; and a kill switch, so a bad plugin is revoked in one row and degrades instead of taking a storefront down.
What you take on
The author agreement, in short: you are an independent developer, you carry your own licence and your own tax, you indemnify Elvoric, you keep the security-disclosure window, you may not claim Elvoric endorses you, and Elvoric may revoke a listing for cause. You are first-line support for what you sell; Elvoric supports the platform, not your plugin. Your plugin is reviewed before it is listed, with its scopes in plain language. And the card rule is absolute: redirect, or your own hosted iframe — Elvoric never renders a card field, and a plugin cannot make it.