Web platform team
We own the dashboard and the generated client it talks to.
| Name | Role |
|---|---|
| Marta Bąk | Engineering lead |
| Chidi Ansah | Senior engineer |
| Sofia Reyes | Engineer |
Slack: #web-platform. No overnight on-call. The dashboard being down is a
next-morning problem, and if payments are actually failing the alert comes
from the payments platform team.
Working with us
We generate the dashboard client from contracts/openapi.json in
cbd-payments-service, at a pinned tag. We write no request or response types
by hand. A payments API change reaches us when someone opens a pull request
that bumps the tag, and the typecheck fails there if the change breaks us.
If you are changing that contract, you do not need to wait for us. Add fields freely. For a rename or a removal, give us a release to move first and say so on the pull request.
Design and copy
Status wording on the payment list is agreed with support and should not be changed without asking them, because they read it out loud to customers. The current wording is in what the dashboard shows.
Things we are asked for a lot
Currency conversion, CSV export of a day’s takings, and a total at the bottom of the list. All three are finance questions rather than support questions, and they are answered by the daily settlement report.