Description

Updates Card feature user-facing terminology from "cashback" to "mUSD back" to align with product language.

Why: The term "cashback" was used inconsistently and doesn't reflect the actual reward mechanism (mUSD tokens).

What changed: 11 locale strings in the English translation file were updated. Internal code (variable names, function names, routes, types) remains unchanged to maintain flexibility if the reward token changes in the future.

Changelog

CHANGELOG entry: Updated Card feature to display "mUSD back" instead of "cashback" in all user-facing text

Related issues

Fixes:

Manual testing steps

Feature: Card mUSD Back terminology

  Scenario: User views MetaMask Card promotional content
    Given user is on a screen showing MetaMask Card benefits

    When user views the card benefits
    Then user sees "mUSD back" terminology instead of "cashback"
    And user sees percentages displayed as "X% mUSD back"

  Scenario: User views Card Home manage options
    Given user has a MetaMask Card linked
    And user is on the Card Home screen

    When user views the manage card options
    Then user sees "mUSD Back" as the rewards option title
    And user sees "Earn X% mUSD back on all spending" as the description

  Scenario: User views mUSD Back withdrawal screen
    Given user has available mUSD back rewards
    And user navigates to the mUSD Back screen

    When user views the screen
    Then user sees "mUSD Back" as the screen title
    And user sees "Available mUSD back" label
    And user sees "No mUSD back available" when balance is zero

Screenshots/Recordings

Before

N/A - Text-only changes in locale file. Strings previously displayed "cashback", "Cashback", "cash back" variants.

After

Updated strings:

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Performance checks (if applicable)

• I've tested on Android
  • N/A - locale string changes only, no runtime impact
• I've tested with a power user scenario
  • N/A - locale string changes only
• I've instrumented key operations with Sentry traces for production performance metrics
  • N/A - no new operations added

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.