Bug: Minimum payment field on credit card should default to family currency

[villancikos]

Where did this bug occur? (required)

• [x ] I am a self-hosted user reporting a bug from my self hosted app
• I am a user of Maybe's paid app

Please note, if you are reporting a bug with sensitive data, please open an Intercom chat from within the app for help

Describe the bug
All the bugs or improvements are reproduced when adding a new Credit Card to the portfolio.

1. Selected MXN as currency. English as language. When adding a new credit card into the portafolio, it doesn't allow "," commas and cents into the fields.
2. The minimum payment field defaults to USD even after selecting MXN as the default currency in the onboarding process.
3. The APR field is normally considered as Percentage. It would be friendly to have the % icon on the right side, so the user avoids adding it thus throwing a formatting error.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'portfolio'
2. Click on 'add credit card'
3. Input number fields with commas and/or cents.
4. Input fields with a percentage %.
5. Selected default is USD instead of following the default on the preferences section.
6. See error
   Expected behavior
   I added the expected behavior above but to reiterate.
   Could be friendly to auto format commas, accept cents and format percentages. Also adding "%" units to the APR field.

Screenshots / Recordings
If applicable, add screenshots or short video recordings to help show the bug in more detail.

[zachgoll]

Hi @villancikos thanks for the report! Let me address each:

1. This is not something that we can support right now. We are using HTML native number input fields which do not support this and due to prioritization do not have plans to change this soon.
2. This is a bug, and I have re-labeled this issue to address it
3. Similar to point 1, this is simply a limitation we have with native HTML number inputs

[villancikos]

My bad, because there is also the USD default "currency" inside this reported bug.
Should I open another one ?

[zachgoll]

@villancikos nope, no need. We can just use this issue for that one!