The Suica rollout: from transit IC to e-money and everyday payments (2001)
From inside the gate to out in the streets
At the centre of this decision is the choice not to keep the contactless IC — technology honed solely to pass people through a fare gate — confined to the ticket. The several-million daily riders of the metropolitan area are an asset other railways cannot easily hold, and it was that density that let Suica widen from a ticket into e-money and mobile payment. Adding uses in stages — from ticket to payment to lifestyle services — reveals a managerial pattern of pointing an existing asset at a different market, rather than launching a one-off new business.
Even so, whether the idea of placing an IC born as a ticket at the centre of an “economic zone” will bear fruit cannot be foreseen as of this writing. The payments market is crowded with code-based and bank-backed services, and there is no guarantee that the transit strength Suica accumulated translates straight into a leading role across everyday life. How far a technology that was self-contained inside the gate can be carried out into the consumption and living of the streets — the question posed by a single card in 2001 remains, a quarter-century on, still open.
Revenue and net margin, FY1996–FY2006
Revenue in ¥ bn (bars) and net margin in % (line), for the years around the decision. Shaded columns are FY2001 onwards — after it was taken.
Source: securities reports
Read the full dossier in Japanese →
The Japanese edition carries the complete record of this decision — the situation that forced it, the options weighed, what actually followed, and the sources behind every claim.
Other key decisions at East Japan Railway
Yen amounts are converted at the average rate of each figure’s own year — not today’s rate; the revenue chart is shown in yen. Exchange rates & sources — the full ¥/US$ table →
Disclaimer
- This page is provided for general information only and is not investment advice, nor a recommendation to buy or sell any security.
- Figures are compiled independently and include our own estimates, approximations and machine-processed data; we make no warranty as to their accuracy or completeness.
- Sources are primarily each company’s securities reports and other public filings, but errors and omissions may remain.
- Any use of this information is at the reader’s own risk. Past performance does not indicate future results.
- Company names, logos and other marks belong to their respective owners.
Data API
East Japan Railway’s history, financials, executives and
shareholders are published as static JSON — no key, plain GET.
Full specification →
| Method | Endpoint | Returns |
|---|---|---|
| GET | /api/companies.json | All companies |
| GET | /api/9020/manifest.json | Resource index |
| GET | /api/9020/history.json | History overview |
| GET | /api/9020/timeline.json | Chronology |
| GET | /api/decisions.json | All management decisions (index) |
| GET | /api/9020/decisions.json | Management decisions (index) |
| GET | /api/9020/decisions/{slug}.json | One decision (full dossier) |
| GET | /api/9020/executives.json | Executives |
| GET | /api/9020/shareholders.json | Major shareholders |
| GET | /api/9020/financials.json | Financial statements |
| GET | /api/9020/financials-longterm.json | Long-term results |
| GET | /api/9020/segments.json | Business segments |
| GET | /api/9020/regions.json | Sales by region |
| GET | /api/9020/workforce.json | Workforce |