Fix internal formatting of monetary values when handling non-decimal currencies #20277
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
As @mattwire pointed out on Mattermost, there is a regression in currency formatting. It arises when processing payments (a) with certain payment processors (e.g. Payflow Pro and iATS) and (b) with currencies that do not use decimal (".") notation.
The problem relates to #20074 (esp 78b338e#diff-3d2a990f0b1960f0b3e6671c645e18033883e6d1eaf535b8d19d085b67dde00bR1171).
Before
Currency separators incorrectly applied
After
The only reason to format money at this stage is to ensure there are 2 decimal places - we should be sticking with machine (US) formatting
Technical Details
Comments
@mattwire @seamuslee001