Fix payment status link in WebUI Rewards panel

[zenparsing]

Resolves brave/brave-browser#25253
Resolves brave/brave-browser#25223

Submitter Checklist:

• I confirm that no security/privacy review is needed, or that I have requested one
• There is a ticket for my issue
• Used Github auto-closing keywords in the PR description above
• Wrote a good PR/commit description
• Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
• Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
• Checked the PR locally: npm run test -- brave_browser_tests, npm run test -- brave_unit_tests, npm run lint, npm run gn_check, npm run tslint
• Ran git rebase master (if needed)

Reviewer Checklist:

• A security review is not needed, or a link to one is included in the PR description
• New files have MPL-2.0 license header
• Adequate test coverage exists to prevent regressions
• Major classes, functions and non-trivial code blocks are well-commented
• Changes in component dependencies are properly reflected in gn
• Code follows the style guide
• Test plan is specified in PR before merging

After-merge Checklist:

• The associated issue milestone is set to the smallest version that the
  changes has landed on
• All relevant documentation has been updated, for instance:
  • https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)
  • https://github.com/brave/brave-browser/wiki/Proxy-redirected-URLs
  • https://github.com/brave/brave-browser/wiki/Fingerprinting-Protections
  • https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
  • https://github.com/brave/brave-browser/wiki/Custom-Headers
  • https://github.com/brave/brave-browser/wiki/Web-Compatibility-Exceptions-in-Brave
  • https://github.com/brave/brave-browser/wiki/QA-Guide
  • https://github.com/brave/brave-browser/wiki/P3A

Test Plan:

The following conditions must be met in order for the UI to be seen:

• The rewards /parameters endpoint must return a payout status of "processing" for user's current wallet type.
• The local machine date should be past the environment payout date (likely the 7th or later).
• The user must have ad rewards for the previous month.

See #14063 (comment) for related test steps and screenshots of affected UI.

[emerick]

LGTM

[LaurenWags]

Verified with

Brave | 1.45.34 Chromium: 105.0.5195.102 (Official Build) nightly (x86_64)
-- | --
Revision | 4c16f5ffcc2da70ee2600d5db77bed423ac03a5a-refs/branch-heads/5195_55@{#4}
OS | macOS Version 12.5.1 (Build 21G83)

Case 1: brave/brave-browser#25253

Unverified - PASSED

Using conditions mentioned in #15018 (comment) as a guide,

• had at least one ad cashed in with the server (redeemed) for September prior to end of month
• had Charles Proxy rules set up to return "processing", "complete", and "off" as needed

1. Advanced device date to Oct 6th (day before payout), launched and confirmed "countdown" message displayed
2. Closed Brave
3. Enabled Charles Proxy rule so that "processing" was returned
4. Advanced device date to Oct 7th (payout day), launched and confirmed "processing" message displayed
5. Confirmed "Check status" link works from webUI panel (ensure proper study, BraveRewardsWebUiPanelStudy:Enabled, is shown on brave://version before checking)
6. Closed Brave
7. Disabled Charles Proxy rule for "processing", and Enabled Charles Proxy rule so that "complete" was returned
8. Launched and confirmed "complete" message is displayed
9. Closed Brave
10. Disabled Charles Proxy rule for "complete", and Enabled Charles Proxy rule so that "off" was returned
11. Launched and confirmed no banner UI is displayed

Step 1	Step 4	Step 5	Step 8	Step 11

Uphold - SKIPPED

Skipped Uphold checks due to error in response from Uphold sandbox. Due to this error, unable to link on staging/sandbox env.

Gemini - PASSED

Using conditions mentioned in #15018 (comment) as a guide,

• had at least one ad cashed in with the server (redeemed) for September prior to end of month
• had Charles Proxy rules set up to return "processing", "complete", and "off" as needed

1. Advanced device date to Oct 6th (day before payout), launched and confirmed "countdown" message displayed
2. Closed Brave
3. Enabled Charles Proxy rule so that "processing" was returned
4. Advanced device date to Oct 7th (payout day), launched and confirmed "processing" message displayed
5. Confirmed "Check status" link works from webUI panel (ensure proper study, BraveRewardsWebUiPanelStudy:Enabled, is shown on brave://version before checking)
6. Closed Brave
7. Disabled Charles Proxy rule for "processing", and Enabled Charles Proxy rule so that "complete" was returned
8. Launched and confirmed "complete" message is displayed
9. Closed Brave
10. Disabled Charles Proxy rule for "complete", and Enabled Charles Proxy rule so that "off" was returned
11. Launched and confirmed no banner UI is displayed

Step 1	Step 4	Step 5	Step 8	Step 11

bitFlyer - PASSED

Pre-req: have region = Japan

Using conditions mentioned in #15018 (comment) as a guide,

• had at least one ad cashed in with the server (redeemed) for September prior to end of month
• had Charles Proxy rules set up to return "processing", "complete", and "off" as needed

1. Advanced device date to Oct 6th (day before payout), launched and confirmed "countdown" message displayed
2. Closed Brave
3. Enabled Charles Proxy rule so that "processing" was returned
4. Advanced device date to Oct 7th (payout day), launched and confirmed "processing" message displayed
5. Confirmed "Check status" link works from webUI panel (ensure proper study, BraveRewardsWebUiPanelStudy:Enabled, is shown on brave://version before checking)
6. Closed Brave
7. Disabled Charles Proxy rule for "processing", and Enabled Charles Proxy rule so that "complete" was returned
8. Launched and confirmed "complete" message is displayed
9. Closed Brave
10. Disabled Charles Proxy rule for "complete", and Enabled Charles Proxy rule so that "off" was returned
11. Launched and confirmed no banner UI is displayed

Step 1	Step 4	Step 5	Step 8	Step 11

Case 2: brave/brave-browser#25223

Reproduced the issue with 1.43.88 and webUI panel enabled, used STR from brave/brave-browser#25223. Clicking on the "Learn more" link did nothing.

Verified resolved with 1.45.34 and STR from brave/brave-browser#25223. Checked "Learn more" link for an unverified creator and a creator who had a different custodial wallet than the one used for Rewards (custodian has Uphold KYC'd wallet, Reward was using Gemini KYC'd custodial wallet).

Example	Example	Example	Example	Example