Bug: Fetches for wrong security when there are multiple security for a given ticker.

[Joelute]

Before you start (required)

General checklist

• I have removed personal / sensitive data from screenshots and logs
• I have searched existing issues and discussions to ensure this is not a duplicate issue

How are you using Maybe?

• I am a paying Maybe customer (hosted version)
  • Paying Maybe users can also open requests in Intercom (if there is sensitive info involved)
• I am a self-hosted user

Self hoster checklist

Paying, hosted users should delete this entire section.

If you are a self-hosted user, please complete all of the information below. Issues with incomplete information will be marked as Needs Info to help our small team prioritize bug fixes.

• Self hosted app commit SHA (find in user menu): [enter commit sha here]
  • I have confirmed that my app's commit is the latest version of Maybe
• Where are you hosting?
  • Render
  • Docker Compose
  • Umbrel
  • Other (please specify)

---

Bug description

When there are multiple securities for a given symbol, it's possible for the app to fetch data for the wrong security rather than the one you desire.

The following securities have the same ticker symbol: CASH
Pathward Financial Inc
Global X High Interest Savings ETF

To Reproduce

Be as specific as possible so Maybe maintainers can quickly reproduce the bug you're experiencing.

Steps to reproduce the behavior:

1. Create an account in CAD currency
2. Create an investment account
3. Add a transaction with the ticker CASH
4. Scroll down and select "Global X High Interest Savings ETF (XTSE)"
5. Wait for the price to be fetched
6. See error in price

Expected behavior

What is the intended behavior that you would expect?

The price of the security should closely resemble the actual price of the security here:
https://www.google.com/finance/quote/CASH:TSE?sa=X&ved=2ahUKEwj95eCR7K-MAxVQhYkEHTNDGqcQ3ecFegQIKRAf

Screenshots and/or recordings

We highly recommend providing additional context with screenshots and/or screen recordings. This will significantly improve the chances of the bug being addressed and fixed quickly.

The following screenshot shows price for:
https://www.google.com/finance/quote/CASH:NASDAQ?sa=X&ved=2ahUKEwjf8_bw7a-MAxWapIkEHRbpJbAQ3ecFegQIOBAf

[zachgoll]

@Joelute thanks for raising this with all these details! I took a look into this, and I believe this may be an error on Synth's end rather than an error with how we're fetching prices on Maybe's end.

I hit Synth directly for CASH | XTSE and got incorrect prices for both the open-close and search endpoints:

I've just opened up an issue on the Synth repo to take a look at this (cc @Shpigford )

[7a6ac0]

@zachgoll If the operating_mic_code is used as a parameter, it will still retrieve the wrong price from synth. However, using mic_code will yield the correct price. Please refer to the screenshot below.

The actual price of the security here:
https://www.google.com/finance/quote/2349:TPE