GREENWAY
The platform
What GREENWAY
actually is.
An infrastructure layer for live commerce: it owns the order, the ticket, the customer record and the ledger, and it calls a processor to move the money.
The fee schedule is data
Nothing below is compiled in. A merchant can hold its own schedule, rules can be added, and the engine refuses to quote at all if the parts stop adding up to the whole. This is the default a fresh install starts with.
| Fee | Kind | Rate | Applied | Paid by |
|---|---|---|---|---|
| Greenway platform fee | platform | 3.00% + $0.99 | per ticket | customer |
| Card processing | processor | 2.90% + $0.30 | per order | organizer |
Processing fees are shown as estimated until the processor reports the real figure at settlement, at which point the ledger writes a correction and the label changes. A platform that shows a settled-looking processing cost it has not been told is guessing with somebody else's payout.
Security posture
Five properties the system holds rather than five things it intends to.
Checkout is hosted by the processor.
A replayed event is refused, not processed twice.
Only the hash is stored, so the database cannot impersonate a user.
Tenancy is enforced in the store as well as the API.
Each one names the actor and the time.
What is and is not built
Listed here rather than left to be discovered. A platform that argues every number should name its source does not get to be vague about its own edges.
Time-based codes, recovery codes and a challenge on sign-in. shipped
The old pass dies the moment the new one is issued. shipped
Bounded mandates, an approval step, and an MCP server. shipped
Entitlements and playback limits exist; no stream provider is connected. part built
Fulfilment is tracked; performance is not measured. planned
The ledger tracks what is owed; settlement is out of band. planned
Tickets carry a seating note, not a map. planned