[richardelms-stash]

https://linear.app/stashgg/issue/ENG-13206/the-public-api-messages-for-spendconversion-and-its-derived-rates

Intent

A partner's tool needs a published wire shape for sending its price row with its loyalty configuration and for reading back what Stash stored: the row itself, the rate derived for each currency, and when the table last changed. Leaving the row out of an update keeps what is stored, and sending an empty one removes it.

flowchart LR
  Tool["Partner tool"] -->|"PUT price row"| Api["Loyalty config API"]
  Api -->|"GET row, rates, updatedAt"| Tool

Loading

^{Beast Intent v0.2.0}

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

---

Note

💥 Blast Radius — Low Risk

Intent: Let a partner's tool submit a loyalty price row and read back the stored row, derived rates and last-change time.

The shared contract is additive: omitting spend_conversion leaves the stored table unchanged.

Overview
UpdateLoyaltyConfig accepts an optional row; configuration responses expose that row, rates_per_usd and updated_at.

Shop reach: Shops with a stored conversion table, count unknown; their configuration responses can include the new field. Writes target the shop named by shop_id.

Data/proto: A tool sends spend_conversion.tiers[].prices → the shop's stored row → rates_per_usd and updated_at in configuration responses. With a table stored, purchases in currencies missing from the row earn no points.

Scope is server/ingress/loyalty/v1/service.proto and two excluded generated files; existing fields remain unchanged.

Not reviewed: 2 generated file(s) — marked linguist-generated in .gitattributes: docs/gen/redoc.ingress.v1.html, docs/gen/swagger.ingress.v1.json.

^{Ripley Review v0.1.0 · 11ff1c3 · Report Issue}