Thanks Erin, this is the case.
Previously, we were going through a series of checks in the app to display the card design (e.g. checking if you’re an investor, or if this is your joint account etc).
Now that we have more card types, it made more sense to rely on a card design ID that comes from the backend because:
- there’s less chance we’ll get the logic wrong in either client
- it’ll match the card that you actually have