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
- No card data reaches GREENWAY — checkout is processor-hosted.
- Webhook signatures are verified and replayed events are refused.
- Sessions are opaque; only their hash is stored.
- Every role is least-privilege, and tenancy is enforced in the store as well as the API.
- Money movement, access changes and ticket voids all write an audit line.
What is not built yet
- Multi-factor authentication — the fields exist, the flow does not.
- Impression and reach measurement for sponsors.
- Automated payouts; the ledger tracks what is owed, settlement is out of band.
- Seat maps and assigned seating.
Listed here rather than left to be discovered.