Number matching is an MFA push check where the user types a number shown on the login screen into their authenticator app to approve the sign-in. Instead of simply tapping approve on a notification, the user has to enter the number displayed on the screen where they are signing in.
It matters because it makes it harder to approve a request by accident or by fatigue. In push bombing attacks, an attacker with a stolen password sends many approval requests in the hope that the user will tap one, and number matching means the user must see the sign-in screen to respond.
It does not stop a relay attack. In an adversary-in-the-middle attack, the victim is looking at the attacker's fake page, which shows the real number, so they may type it in believing the sign-in is theirs. It improves on a plain push approval but is weaker than methods that are tied to the real site's domain.
To use it, turn it on wherever push approval is used, treat it as a step up from simple approval and move high-risk accounts to phishing-resistant methods.