Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Uphold /capabilities endpoint spec changed — need to adjust get_capabilities #23849

Closed
szilardszaloki opened this issue Jul 2, 2022 · 7 comments · Fixed by brave/brave-core#14057
Closed

Uphold /capabilities endpoint spec changed — need to adjust get_capabilities #23849

szilardszaloki opened this issue Jul 2, 2022 · 7 comments · Fixed by brave/brave-core#14057
Assignees
@szilardszaloki
Labels
feature/rewards OS/Android Fixes related to Android browser functionality OS/Desktop priority/P1 A very extremely bad problem. We might push a hotfix for it. QA Pass - Android Tab QA Pass-Win64 QA/Yes release-notes/exclude
Milestone
1.42.x - Release

Comments

@szilardszaloki
Copy link
Contributor

Description

Due to a specification change of Uphold's /capabilities endpoint, users that are required to provide information to Uphold (e.g. CDD, EDD, etc.) are now allowed to verify with Uphold, although they cannot send (tip), and/or receive (monthly payouts).

Miscellaneous Information:

cc: @Miyayes @brave/rewards-client
@szilardszaloki szilardszaloki self-assigned this Jul 2, 2022
@Miyayes Miyayes added feature/rewards priority/P1 A very extremely bad problem. We might push a hotfix for it. labels Jul 2, 2022
@Miyayes
Copy link
Collaborator

Miyayes commented Jul 2, 2022

Does this need a separate Android implementation?

@szilardszaloki
Copy link
Contributor Author

No, the desktop change will take care of it on Android, too.

@szilardszaloki szilardszaloki added OS/Android Fixes related to Android browser functionality QA/Yes release-notes/exclude labels Jul 2, 2022
@szilardszaloki szilardszaloki mentioned this issue Jul 5, 2022
Merged
25 tasks
@brave-builds brave-builds added this to the 1.43.x - Nightly milestone Jul 7, 2022
@brave-builds brave-builds mentioned this issue Jul 7, 2022
Merged
7 tasks
@kjozwiak
Copy link
Member

The above will require 1.42.67 or higher for 1.42.x verification 👍

@LaurenWags LaurenWags added the QA/In-Progress Indicates that QA is currently in progress for that particular issue label Jul 15, 2022
@GeetaSarvadnya
Copy link

GeetaSarvadnya commented Jul 15, 2022 •
edited
Loading

Verification PASSED on

Brave | 1.42.68 Chromium: 103.0.5060.114 (Official Build) beta (64-bit)
-- | --
Revision | a1c2360c5b02a6d4d6ab33796ad8a268a6128226-refs/branch-heads/5060@{#1124}
OS | Windows 10 Version 21H2 (Build 19044.1826)
Case 1 - Sufficient capabilities - PASSED

Scenario 1 - Clean profile - PASSED

  1. Launched with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account that has sufficient capabilities
  3. Confirmed /v0/me/capabilities returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
[ REQUEST ]
> URL: https://api-sandbox.uphold.com/v0/me/capabilities
> Method: GET
[19628:12540:0716/164942.264:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
> Url: https://api-sandbox.uphold.com/v0/me/capabilities
> Result: Success
> HTTP Code: 200
> Body: 

{
"category":"permissions",
"enabled":true,
"key":"receives",
"name":"Receives",
"requirements":[],
"restrictions":[]
},

{
"category":"permissions",
"enabled":true,
"key":"sends",
"name":"Sends",
"requirements":[],
"restrictions":[]
},
  1. Confirmed balance displayed on brave://rewards and panel
  2. Confirmed no notifications/messages about needing to complete additional requirements
Example Example
image image

Scenario 2 - Upgrade profile - on brave://rewards page prior to Upgrade - PASSED

  1. Launched 1.41.x with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account that has sufficient capabilities
  3. Confirmed /v0/me/capabilities returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  4. Confirmed balance displayed on brave://rewards and panel
  5. Ensured brave://rewards page was active tab
  6. Closed 1.41.x and "Upgraded" version (renamed profile)
  7. Launched with upgraded version
  8. Confirmed /v0/me/capabilities still returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
[ REQUEST ]
> URL: https://api-sandbox.uphold.com/v0/me/capabilities
> Method: GET
[19128:13764:0718/121921.819:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
> Url: https://api-sandbox.uphold.com/v0/me/capabilities
> Result: Success
> HTTP Code: 200
> Body: [

{
"category":"permissions",
"enabled":true,
"key":"receives",
"name":"Receives",
"requirements":[],
"restrictions":[]
},
{"category":"permissions",
"enabled":true,"key":
"sends","name":
"Sends","requirements":[],
"restrictions":[]
},
]
  1. Confirmed balance displayed on brave://rewards and panel
  2. Confirmed no notifications/messages about needing to complete additional requirements

Scenario 3 - Upgrade profile - brave://rewards page is not open prior to Upgrade - PASSED

  1. Launched 1.41.x with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account that has sufficient capabilities
  3. Confirmed /v0/me/capabilities returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  4. Confirmed balance displayed on brave://rewards and panel
  5. Ensured brave://rewards page was not open
  6. Closed 1.41.x and "Upgraded" version (renamed profile)
  7. Launched with upgraded version
  8. Confirmed /v0/me/capabilities still returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
[ REQUEST ]
> URL: https://api-sandbox.uphold.com/v0/me/capabilities
> Method: GET
[19128:13764:0718/121921.819:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
> Url: https://api-sandbox.uphold.com/v0/me/capabilities
> Result: Success
> HTTP Code: 200
> Body: [

{
"category":"permissions",
"enabled":true,
"key":"receives",
"name":"Receives",
"requirements":[],"restrictions":[]
},
{"category":"permissions",
"enabled":true,"key":
"sends","name":
"Sends","requirements":[],"restrictions":[]
},
]
  1. Confirmed balance displayed on panel
  2. Confirmed no notifications/messages about needing to complete additional requirements
Case 2 - Insufficient capabilities, receives=1 with requirements - PASSED

Scenario 1 - Clean profile - PASSED

  1. Configured a Charles Proxy rule for the body of /v0/me/capabilities as per Implements Uphold /capabilities spec change. brave-core#14057 (comment), ensure rule is running
  2. Launched with a clean profile and staging env
  3. Enabled Rewards and linked Uphold account
  4. Confirmed /v0/me/capabilities was overwritten per the Charles Proxy rule as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
[ REQUEST ]
> URL: https://api-sandbox.uphold.com/v0/me/capabilities
> Method: GET
[16172:3024:0718/213106.546:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
> Url: https://api-sandbox.uphold.com/v0/me/capabilities
> Result: Success
> HTTP Code: 200
> Body: [  

{     
    "category": "permissions", 
    "enabled": true,   
	"key": "receives", 
    "name": "Receives", 
    "requirements": ["user-must-submit-customer-due-diligence"],  
	"restrictions": []  
},  

{     
 "category": "permissions",   
 "enabled": true,    
 "key": "sends",    
 "name": "Sends", 
 "requirements": [],  
 "restrictions": [] 
},  
]
  1. Confirmed message displayed on brave://rewards page
  2. Confirmed no notification on BAT logo in URL bar
  3. Confirmed balance not shown on brave://rewards page or panel
  4. Confirmed status was as expected on brave://rewards-internals
Example Example
image image

Scenario 2 - Upgrade profile - on brave://rewards page prior to Upgrade - PASSED

  1. Using same Charles Proxy rule from "Clean Profile" case for this scenario, launched 1.41.x with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account
  3. Confirmed balance displayed on brave://rewards and panel
  4. Confirmed /v0/me/capabilities returned as expected for this case per Charles Proxy rule written as per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  5. Ensured brave://rewards page was active tab
  6. Closed 1.41.x
  7. "Upgraded" version (renamed profile) and Launched with upgraded version
  8. Confirmed /v0/me/capabilities still returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
[ REQUEST ]
> URL: https://api-sandbox.uphold.com/v0/me/capabilities
> Method: GET
[20688:21352:0718/215454.515:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
> Url: https://api-sandbox.uphold.com/v0/me/capabilities
> Result: Success
> HTTP Code: 200
> Body: [   
  {    
  "category": "permissions", 
  "enabled": true, 
  "key": "receives",  
  "name": "Receives", 
  "requirements": ["user-must-submit-customer-due-diligence"],
  "restrictions": []  
  },  
  {   
  "category": "permissions", 
  "enabled": true, 
  "key": "sends",  
  "name": "Sends", 
  "requirements": [], 
  "restrictions": [] 
  },
  1. Confirmed modal and notification (on BAT logo) are shown
  2. Confirmed balance no longer displayed on rewards page or panel
  3. Confirmed status was as expected on brave://rewards-internals (VERIFIED --> NOT CONNECTED)
  4. Confirmed logs showed the below as per the PR:
[ REQUEST ]
> URL: https://grant.rewards.bravesoftware.com/v3/wallet/uphold/7b6297cd-10cc-400d-8532-f2db1d4eec90/claim
> Method: DEL
> Content Type: application/json; charset=utf-8
> Header digest: SHA-256=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=
> Header signature: keyId="7b6297cd-10cc-400d-8532-f2db1d4eec90",algorithm="ed25519",headers="digest (request-target)",signature="LyO5qWh9PTUemJ1zGTNo8FXXAuu8qGzQNJIAgNsCcxYUQ4BHxNIKyLbtLQ7MOnmoadpUSbXIhYgdAQsOoTjoDQ=="
> Header accept: application/json

[ RESPONSE HEADERS ]
> Url: https://grant.rewards.bravesoftware.com/v3/wallet/uphold/7b6297cd-10cc-400d-8532-f2db1d4eec90/claim

> Header content-length: 5
> Header content-type: application/json
> Header date: Mon, 18 Jul 2022 16:30:55 GMT
> Header request-id: cbaolfus5n19d4npotig
> Header via: 1.1 9bebc00fac9e8d2cc595108150da6404.cloudfront.net (CloudFront)
> Header x-amz-cf-id: wGnuibAw9UapSBXCyhHfhpiNgB34TorkyBFuuLPaEweP2bsIZoJcHQ==
> Header x-amz-cf-pop: MAA51-P2
> Header x-cache: Miss from cloudfront
> Header x-request-id: 7pAtTjkLByG7V6wM
[6860:14788:0718/220055.796:VERBOSE1:uphold.cc(186)] Disconnecting wallet
Example Example Example
image image image

Scenario 3 - Upgrade profile - brave://rewards page is not open prior to Upgrade - PASSED

  1. Using same Charles Proxy rule from "Clean Profile" case for this scenario, launched 1.41.x with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account
  3. Confirmed balance displayed on brave://rewards and panel
  4. Confirmed /v0/me/capabilities returned as expected for this case per Charles Proxy rule written as per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  5. Ensured brave://rewards page was not open tab
  6. Closed 1.41.x
  7. "Upgraded" version (renamed profile) and Launched with upgraded version
  8. Confirmed /v0/me/capabilities still returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
[ REQUEST ]
> URL: https://api-sandbox.uphold.com/v0/me/capabilities
> Method: GET
[22936:9660:0718/220806.666:VERBOSE1:browser_manager.cc(53)] Browser did become active
[22936:9660:0718/220806.668:VERBOSE6:user_activity_manager.cc(48)] Triggered event: 16 (1:2:3600 s)
[22936:9660:0718/220806.678:VERBOSE7:tab_manager.cc(66)] Tab id 2 is occluded
[22936:9660:0718/220806.679:VERBOSE2:tab_manager.cc(95)] Tab id 3 was updated
[22936:9660:0718/220806.680:VERBOSE6:user_activity_manager.cc(48)] Triggered event: 11 (1:2:3600 s)
[22936:9660:0718/220807.025:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
> Url: https://api-sandbox.uphold.com/v0/me/capabilities
> Result: Success
> HTTP Code: 200
> Body: [   
{ 
    "category": "permissions",  
	"enabled": true,   
	"key": "receives", 
    "name": "Receives",  
	"requirements": ["user-must-submit-customer-due-diligence"],  
	"restrictions": []  
	},  
	{     
	"category": "permissions",  
	"enabled": true, 
    "key": "sends",  
	"name": "Sends", 
    "requirements": [],   
	"restrictions": [] 
	},  
	
]
  1. Confirmed only notification (on BAT logo) is shown (no modal)
  2. Confirmed balance no longer displayed on rewards page or panel
  3. Confirmed status was as expected on brave://rewards-internals (VERIFIED --> NOT CONNECTED)
  4. Confirmed logs showed the below as per the PR:
[ REQUEST ]
> URL: https://grant.rewards.bravesoftware.com/v3/wallet/uphold/86ebe20b-e84d-4cbd-a10c-14f565888e94/claim
> Method: DEL
> Content Type: application/json; charset=utf-8
> Header digest: SHA-256=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=
> Header signature: keyId="86ebe20b-e84d-4cbd-a10c-14f565888e94",algorithm="ed25519",headers="digest (request-target)",signature="uYQDv6dDQlGOuQhA6VKmuYBChmqrbt4wM7Cct5iEKgsPCCMWb9NYFK2dU7JvEWxwV0Ho19SP/3Vor50fZDCZCA=="
> Header accept: application/json
[15008:22852:0718/221210.840:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
> Url: https://grant.rewards.bravesoftware.com/v3/wallet/uphold/86ebe20b-e84d-4cbd-a10c-14f565888e94/claim
> Result: Success
> HTTP Code: 200
> Body: null

[15008:22852:0718/221210.841:VERBOSE9:logging_util.cc(138)]
[ RESPONSE HEADERS ]
> Url: https://grant.rewards.bravesoftware.com/v3/wallet/uphold/86ebe20b-e84d-4cbd-a10c-14f565888e94/claim

> Header content-length: 5
> Header content-type: application/json
> Header date: Mon, 18 Jul 2022 16:42:10 GMT
> Header request-id: cbaoqoms5n19d4npotmg
> Header via: 1.1 1880ddcc9891efa57732d51c211bba32.cloudfront.net (CloudFront)
> Header x-amz-cf-id: n6PnipBHc72kvJWMrkTVckj10gyVJBJGIhi8WQ0_kzi8StfgfZxQVA==
> Header x-amz-cf-pop: MAA51-P2
> Header x-cache: Miss from cloudfront
> Header x-request-id: EAtaVrJ2oVRG88y1
[15008:22852:0718/221210.855:VERBOSE1:uphold.cc(186)] Disconnecting wallet
Example Example
image image
Case 3 - Insufficient capabilities, receives=2 - PASSED

Scenario 1 - Clean profile - PASSED

  1. Configured a Charles Proxy rule for the body of /v0/me/capabilities as per Implements Uphold /capabilities spec change. brave-core#14057 (comment), ensure rule is running
  2. Launched with a clean profile and staging env
  3. Enabled Rewards and linked Uphold account
  4. Confirmed /v0/me/capabilities was overwritten per the Charles Proxy rule as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
[ REQUEST ]
> URL: https://api-sandbox.uphold.com/v0/me/capabilities
> Method: GET
[2496:14444:0718/152524.978:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
> Url: https://api-sandbox.uphold.com/v0/me/capabilities
> Result: Success
> HTTP Code: 200
> Body: [  

{  
   "category": "permissions",   
  "enabled": false, 
  "key": "receives",   
  "name": "Receives", 
  "requirements": [], 
  "restrictions": []  
},  

{   
  "category": "permissions",   
  "enabled": true,   
  "key": "sends",  
  "name": "Sends",  
  "requirements": [],  
  "restrictions": []  
},
  1. Confirmed message displayed on brave://rewards page
  2. Confirmed no notification on BAT logo in URL bar
  3. Confirmed balance not shown on brave://rewards page or panel
  4. Confirmed status was as expected on brave://rewards-internals
Example Example
image image

Scenario 2 - Upgrade profile - on brave://rewards page prior to Upgrade - PASSED

  1. Using same Charles Proxy rule from "Clean Profile" case for this scenario, launched 1.41.x with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account
  3. Confirmed /v0/me/capabilities returned as expected for this case per Charles Proxy rule written as per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  4. Confirm unable to verify wallet due to "sends" or "receives" being false (implemented with previously with Implement error modal if user does not have receives OR sends capabilities on Uphold #22508)
  • modal with message is shown
  • no balance displayed on rewards page or panel
  1. Ensured brave://rewards page was active tab
  2. Closed 1.41.x
  3. "Upgraded" version (renamed profile) and Launched with upgraded version
  4. Confirmed status was as expected on brave://rewards-internals (still NOT CONNECTED)
  5. Attempt to link account again (with Charles Proxy still running the rewrite rule)
  6. Confirmed /v0/me/capabilities still returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
[ REQUEST ]
> URL: https://api-sandbox.uphold.com/v0/me/capabilities
> Method: GET
[2496:14444:0718/152524.978:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
> Url: https://api-sandbox.uphold.com/v0/me/capabilities
> Result: Success
> HTTP Code: 200
> Body: [  

{  
   "category": "permissions",   
  "enabled": false, 
  "key": "receives",   
  "name": "Receives", 
  "requirements": [], 
  "restrictions": []  
},  

{   
  "category": "permissions",   
  "enabled": true,   
  "key": "sends",  
  "name": "Sends",  
  "requirements": [],  
  "restrictions": []  
},
  1. Confirmed modal message is shown
  2. Confirmed balance not displayed on rewards page or panel
  3. Confirmed status was as expected on brave://rewards-internals (still NOT CONNECTED)
Example Example
image image

Scenario 3 - Upgrade profile - brave://rewards page not open prior to Upgrade - PASSED

  1. Using same Charles Proxy rule from "Clean Profile" case for this scenario, launched 1.41.x with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account
  3. Confirmed /v0/me/capabilities returned as expected for this case per Charles Proxy rule written as per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  4. Confirm unable to verify wallet due to "sends" or "receives" being false (implemented with previously with Implement error modal if user does not have receives OR sends capabilities on Uphold #22508)
  • modal with message is shown
  • no balance displayed on rewards page or panel
  1. Ensured brave://rewards page was not open
  2. Closed 1.41.x
  3. "Upgraded" version (renamed profile) and Launched with upgraded version
  4. Confirmed status was as expected on brave://rewards-internals (still NOT CONNECTED)
  5. Attempt to link account again (with Charles Proxy still running the rewrite rule)
  6. Confirmed /v0/me/capabilities still returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
[ REQUEST ]
> URL: https://api-sandbox.uphold.com/v0/me/capabilities
> Method: GET
[9068:7656:0718/154553.178:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
> Url: https://api-sandbox.uphold.com/v0/me/capabilities
> Result: Success
> HTTP Code: 200
> Body: [  

{     
 "category": "permissions", 
 "enabled": false,
 "key": "receives",   
 "name": "Receives",     
 "requirements": [],  
 "restrictions": []  
 },   
 
{    
 "category": "permissions", 
 "enabled": true,  
 "key": "sends",  
 "name": "Sends", 
 "requirements": [],  
 "restrictions": []
 },  
]
  1. Confirmed modal message is shown
  2. Confirmed balance not displayed on rewards page or panel
  3. Confirmed status was as expected on brave://rewards-internals (still NOT CONNECTED)
Example Example
image image
Case 4 - Insufficient capabilities, sends=1 with requirements - PASSED

Scenario 1 - Clean profile - PASSED

  1. Configured a Charles Proxy rule for the body of /v0/me/capabilities as per Implements Uphold /capabilities spec change. brave-core#14057 (comment), ensure rule is running
  2. Launched with a clean profile and staging env
  3. Enabled Rewards and linked Uphold account
  4. Confirmed /v0/me/capabilities was overwritten per the Charles Proxy rule as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
[ RESPONSE - OnRequest ]
> Url: https://api-sandbox.uphold.com/v0/me/capabilities
> Result: Success
> HTTP Code: 200
> Body: [   
{   
  "category": "permissions", 
  "enabled": true,  
  "key": "receives",   
  "name": "Receives", 
  "requirements": [], 
  "restrictions": [] 
  },  
  {   
  "category": "permissions",  
  "enabled": true,  
  "key": "sends",  
  "name": "Sends", 
  "requirements": ["user-must-submit-customer-due-diligence"],  
  "restrictions": [] 
  },
  1. Confirmed message displayed on brave://rewards page
  2. Confirmed no notification on BAT logo in URL bar
  3. Confirmed balance not shown on brave://rewards page or panel
  4. Confirmed status was as expected on brave://rewards-internals
Example Example
image image

Scenario 2 - Upgrade profile - on brave://rewards page prior to Upgrade - PASSED

  1. Using same Charles Proxy rule from "Clean Profile" case for this scenario, launched 1.41.x with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account
  3. Confirmed balance displayed on brave://rewards and panel
  4. Confirmed /v0/me/capabilities returned as expected for this case per Charles Proxy rule written as per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  5. Ensured brave://rewards page was active tab
  6. Closed 1.41.x
  7. "Upgraded" version (renamed profile) and Launched with upgraded version
  8. Confirmed /v0/me/capabilities still returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
[ REQUEST ]
> URL: https://api-sandbox.uphold.com/v0/me/capabilities
> Method: GET
[15684:14064:0718/222854.385:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
> Url: https://api-sandbox.uphold.com/v0/me/capabilities
> Result: Success
> HTTP Code: 200
> Body: [   
 {    
 "category": "permissions", 
 "enabled": true,  
 "key": "receives", 
 "name": "Receives", 
 "requirements": [],  
 "restrictions": []  
 },   
 {  
 "category": "permissions",
 "enabled": true,  
 "key": "sends",  
 "name": "Sends", 
 "requirements": ["user-must-submit-customer-due-diligence"], 
 "restrictions": [] 
 },  
 ]
  1. Confirmed modal and notification (on BAT logo) are shown
  2. Confirmed balance no longer displayed on rewards page or panel
  3. Confirmed status was as expected on brave://rewards-internals (VERIFIED --> NOT CONNECTED)
  4. Confirmed logs showed the below as per the PR:

[ REQUEST ]
> URL: https://grant.rewards.bravesoftware.com/v3/wallet/uphold/4b7e7a11-f548-4c15-bc93-bfd31d68f7d3/claim
> Method: DEL
> Content Type: application/json; charset=utf-8
> Header digest: SHA-256=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=
> Header signature: keyId="4b7e7a11-f548-4c15-bc93-bfd31d68f7d3",algorithm="ed25519",headers="digest (request-target)",signature="y9tQOWo6xhRfdlbSgPc0YeUr9gcp5/EUPYaUY7XAVxcafi+NmVlTZNX5rVWbqDqqm1XufaMEZZ83YtsmD9hpCA=="
> Header accept: application/json

[ RESPONSE - OnRequest ]
> Url: https://grant.rewards.bravesoftware.com/v3/wallet/uphold/4b7e7a11-f548-4c15-bc93-bfd31d68f7d3/claim
> Result: Success
> HTTP Code: 200
> Body: null

[9224:18648:0718/223142.011:VERBOSE9:logging_util.cc(138)]
[ RESPONSE HEADERS ]
> Url: https://grant.rewards.bravesoftware.com/v3/wallet/uphold/4b7e7a11-f548-4c15-bc93-bfd31d68f7d3/claim

> Header content-length: 5
> Header content-type: application/json
> Header date: Mon, 18 Jul 2022 17:01:41 GMT
> Header request-id: cbap3tes5n19d4npotsg
> Header via: 1.1 2b757d4b6323f221fdd6ec1353386e76.cloudfront.net (CloudFront)
> Header x-amz-cf-id: wfuaUc2MznHTw3V4uCkfbxQc-FSGCrIxn4GP2pEQOoNcffMHfgrAAA==
> Header x-amz-cf-pop: MAA51-P2
> Header x-cache: Miss from cloudfront
> Header x-request-id: F5cDid6etsdNRDMf
[9224:18648:0718/223142.019:VERBOSE1:uphold.cc(186)] Disconnecting wallet
Example Example Example
image image image

Scenario 3 - Upgrade profile - brave://rewards page is not open prior to Upgrade - PASSED

  1. Using same Charles Proxy rule from "Clean Profile" case for this scenario, launched 1.41.x with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account
  3. Confirmed balance displayed on brave://rewards and panel
  4. Confirmed /v0/me/capabilities returned as expected for this case per Charles Proxy rule written as per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  5. Ensured brave://rewards page was not open tab
  6. Closed 1.41.x
  7. "Upgraded" version (renamed profile) and Launched with upgraded version
  8. Confirmed /v0/me/capabilities still returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
[ REQUEST ]
> URL: https://api-sandbox.uphold.com/v0/me/capabilities
> Method: GET
[14708:3968:0718/223727.993:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
> Url: https://api-sandbox.uphold.com/v0/me/capabilities
> Result: Success
> HTTP Code: 200
> Body: [   
 {    
 "category": "permissions",  
 "enabled": true,    
 "key": "receives",  
 "name": "Receives", 
 "requirements": [],  
 "restrictions": []  
 },   
 {   
 "category": "permissions", 
 "enabled": true,    
 "key": "sends",  
 "name": "Sends",  
 "requirements": ["user-must-submit-customer-due-diligence"], 
 "restrictions": []   
 },  
]
  1. Confirmed only notification (on BAT logo) is shown (no modal)
  2. Confirmed balance no longer displayed on rewards page or panel
  3. Confirmed status was as expected on brave://rewards-internals (VERIFIED --> NOT CONNECTED)
  4. Confirmed logs showed the below as per the PR:
[ REQUEST ]
> URL: https://grant.rewards.bravesoftware.com/v3/wallet/uphold/44459201-72bb-4e11-9ebb-d101dcdfa022/claim
> Method: DEL
> Content Type: application/json; charset=utf-8
> Header digest: SHA-256=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=
> Header signature: keyId="44459201-72bb-4e11-9ebb-d101dcdfa022",algorithm="ed25519",headers="digest (request-target)",signature="U65X7V84Ad5eviIyptDYi0PcbmhVMNtTHM3lsqjXTzgzA9uea9OMoeSK5iuq6vb5oxnQanNiKMy+y4uTrFQKDQ=="
> Header accept: application/json
[23048:1792:0718/224017.417:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
> Url: https://grant.rewards.bravesoftware.com/v3/wallet/uphold/44459201-72bb-4e11-9ebb-d101dcdfa022/claim
> Result: Success
> HTTP Code: 200
> Body: null

[23048:1792:0718/224017.418:VERBOSE9:logging_util.cc(138)]
[ RESPONSE HEADERS ]
> Url: https://grant.rewards.bravesoftware.com/v3/wallet/uphold/44459201-72bb-4e11-9ebb-d101dcdfa022/claim

> Header content-length: 5
> Header content-type: application/json
> Header date: Mon, 18 Jul 2022 17:10:16 GMT
> Header request-id: cbap7u6s5n19d4npou20
> Header via: 1.1 4b6cf9d0cfb56136d982f36d2a172b1a.cloudfront.net (CloudFront)
> Header x-amz-cf-id: fKuNqI39Xi9k8mBirs7zq-h7avLMcVFz0YExlREmmr19QG7QEKSG6g==
> Header x-amz-cf-pop: MAA51-P2
> Header x-cache: Miss from cloudfront
> Header x-request-id: 5fYm4HPLVRm6Wyyt
[23048:1792:0718/224017.433:VERBOSE1:uphold.cc(186)] Disconnecting wallet
Example Example
image image
Case 5 - Insufficient capabilities, sends=2 - PASSED

Scenario 1 - Clean profile - PASSED

  1. Configured a Charles Proxy rule for the body of /v0/me/capabilities as per Implements Uphold /capabilities spec change. brave-core#14057 (comment), ensure rule is running
  2. Launched with a clean profile and staging env
  3. Enabled Rewards and linked Uphold account
  4. Confirmed /v0/me/capabilities was overwritten per the Charles Proxy rule as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
[ REQUEST ]
> URL: https://api-sandbox.uphold.com/v0/me/capabilities
> Method: GET
[6536:13696:0718/161439.160:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
> Url: https://api-sandbox.uphold.com/v0/me/capabilities
> Result: Success
> HTTP Code: 200
> Body: [  

{    
   "category": "permissions",  
   "enabled": true,
   "key": "receives", 
   "name": "Receives",  
   "requirements": [],  
   "restrictions": []  
   
},   
{     
  "category": "permissions",   
  "enabled": false,  
  "key": "sends",  
  "name": "Sends", 
  "requirements": [],   
  "restrictions": []  
},
  1. Confirmed message displayed on brave://rewards page
  2. Confirmed no notification on BAT logo in URL bar
  3. Confirmed balance not shown on brave://rewards page or panel
  4. Confirmed status was as expected on brave://rewards-internals
Example Example
image image

Scenario 2 - Upgrade profile - on brave://rewards page prior to Upgrade - PASSED

  1. Using same Charles Proxy rule from "Clean Profile" case for this scenario, launched 1.41.x with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account
  3. Confirmed /v0/me/capabilities returned as expected for this case per Charles Proxy rule written as per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  4. Confirm unable to verify wallet due to "sends" or "receives" being false (implemented with previously with Implement error modal if user does not have receives OR sends capabilities on Uphold #22508)
  • modal with message is shown
  • no balance displayed on rewards page or panel
  1. Ensured brave://rewards page was active tab
  2. Closed 1.41.x
  3. "Upgraded" version (renamed profile) and Launched with upgraded version
  4. Confirmed status was as expected on brave://rewards-internals (still NOT CONNECTED)
  5. Attempt to link account again (with Charles Proxy still running the rewrite rule)
  6. Confirmed /v0/me/capabilities still returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
[ REQUEST ]
> URL: https://api-sandbox.uphold.com/v0/me/capabilities
> Method: GET
[16736:12696:0718/162824.441:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
> Url: https://api-sandbox.uphold.com/v0/me/capabilities
> Result: Success
> HTTP Code: 200
> Body: [  

 {   
 "category": "permissions",  
 "enabled": true,   
 "key": "receives",  
 "name": "Receives",  
 "requirements": [],  
 "restrictions": []  
 },   
 {   
 "category": "permissions", 
 "enabled": false,   
 "key": "sends",    
 "name": "Sends",  
 "requirements": [],   
 "restrictions": []  
 },  
  
]
  1. Confirmed modal message is shown
  2. Confirmed balance not displayed on rewards page or panel
  3. Confirmed status was as expected on brave://rewards-internals (still NOT CONNECTED)
Example Example
image image

Scenario 3 - Upgrade profile - brave://rewards page not open prior to Upgrade - PASSED

  1. Using same Charles Proxy rule from "Clean Profile" case for this scenario, launched 1.41.x with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account
  3. Confirmed /v0/me/capabilities returned as expected for this case per Charles Proxy rule written as per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  4. Confirm unable to verify wallet due to "sends" or "receives" being false (implemented with previously with Implement error modal if user does not have receives OR sends capabilities on Uphold #22508)
  • modal with message is shown
  • no balance displayed on rewards page or panel
  1. Ensured brave://rewards page was not open
  2. Closed 1.41.x
  3. "Upgraded" version (renamed profile) and Launched with upgraded version
  4. Confirmed status was as expected on brave://rewards-internals (still NOT CONNECTED)
  5. Attempt to link account again (with Charles Proxy still running the rewrite rule)
  6. Confirmed /v0/me/capabilities still returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
[ REQUEST ]
> URL: https://api-sandbox.uphold.com/v0/me/capabilities
> Method: GET
[13308:20120:0718/164103.988:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
> Url: https://api-sandbox.uphold.com/v0/me/capabilities
> Result: Success
> HTTP Code: 200
> Body: [  
{    
 "category": "permissions",    
 "enabled": true,  
 "key": "receives",  
 "name": "Receives",  
 "requirements": [],  
 "restrictions": []  
 },  

 {   
 "category": "permissions",  
 "enabled": false,  
 "key": "sends",   
 "name": "Sends",  
 "requirements": [],  
 "restrictions": []   
 },  
 
 ]
  1. Confirmed modal message is shown
  2. Confirmed balance not displayed on rewards page or panel
  3. Confirmed status was as expected on brave://rewards-internals (still NOT CONNECTED)
Example Example
image image
Case 6 - Insufficient capabilities, receives=1 with requirements, sends=2 - PASSED

Scenario 1 - Clean profile - PASSED

  1. Configured a Charles Proxy rule for the body of /v0/me/capabilities as per Implements Uphold /capabilities spec change. brave-core#14057 (comment), ensure rule is running
  2. Launched with a clean profile and staging env
  3. Enabled Rewards and linked Uphold account
  4. Confirmed /v0/me/capabilities was overwritten per the Charles Proxy rule as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
[ REQUEST ]
> URL: https://api-sandbox.uphold.com/v0/me/capabilities
> Method: GET
[17732:19748:0718/165207.620:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
> Url: https://api-sandbox.uphold.com/v0/me/capabilities
> Result: Success
> HTTP Code: 200
> Body: [  

 {    
 "category": "permissions",   
 "enabled": true,   
 "key": "receives", 
 "name": "Receives", 
 "requirements": [ "user-must-submit-customer-due-diligence" ], 
 "restrictions": [] 
 },   
 {   
 "category": "permissions",  
 "enabled": false, 
 "key": "sends",   
 "name": "Sends",  
 "requirements": [], 
 "restrictions": []  
 }, 
]
  1. Confirmed message displayed on brave://rewards page
  2. Confirmed no notification on BAT logo in URL bar
  3. Confirmed balance not shown on brave://rewards page or panel
  4. Confirmed status was as expected on brave://rewards-internals
Example Example
image image

Scenario 2 - Upgrade profile - on brave://rewards page prior to Upgrade - PASSED

  1. Using same Charles Proxy rule from "Clean Profile" case for this scenario, launched 1.41.x with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account
  3. Confirmed /v0/me/capabilities returned as expected for this case per Charles Proxy rule written as per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  4. Confirm unable to verify wallet due to "sends" or "receives" being false (implemented with previously with Implement error modal if user does not have receives OR sends capabilities on Uphold #22508)
  • modal with message is shown
  • no balance displayed on rewards page or panel
  1. Ensured brave://rewards page was active tab
  2. Closed 1.41.x
  3. "Upgraded" version (renamed profile) and Launched with upgraded version
  4. Confirmed status was as expected on brave://rewards-internals (still NOT CONNECTED)
  5. Attempt to link account again (with Charles Proxy still running the rewrite rule)
  6. Confirmed /v0/me/capabilities still returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
[ REQUEST ]
> URL: https://api-sandbox.uphold.com/v0/me/capabilities
> Method: GET
[17176:8900:0718/170015.963:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
> Url: https://api-sandbox.uphold.com/v0/me/capabilities
> Result: Success
> HTTP Code: 200
> Body: [   

 {    
 "category": "permissions", 
 "enabled": true, 
 "key": "receives",  
 "name": "Receives", 
 "requirements": [ "user-must-submit-customer-due-diligence" ], 
 "restrictions": [] 
 },  
 {     
 "category": "permissions",  
 "enabled": false,   
 "key": "sends",  
 "name": "Sends", 
 "requirements": [],  
 "restrictions": []  
 },  
]
  1. Confirmed modal message is shown
  2. Confirmed balance not displayed on rewards page or panel
  3. Confirmed status was as expected on brave://rewards-internals (still NOT CONNECTED)
Example Example
image image

Scenario 3 - Upgrade profile - brave://rewards page not open prior to Upgrade - PASSED

  1. Using same Charles Proxy rule from "Clean Profile" case for this scenario, launched 1.41.x with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account
  3. Confirmed /v0/me/capabilities returned as expected for this case per Charles Proxy rule written as per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  4. Confirm unable to verify wallet due to "sends" or "receives" being false (implemented with previously with Implement error modal if user does not have receives OR sends capabilities on Uphold #22508)
  • modal with message is shown
  • no balance displayed on rewards page or panel
  1. Ensured brave://rewards page was not open
  2. Closed 1.41.x
  3. "Upgraded" version (renamed profile) and Launched with upgraded version
  4. Confirmed status was as expected on brave://rewards-internals (still NOT CONNECTED)
  5. Attempt to link account again (with Charles Proxy still running the rewrite rule)
  6. Confirmed /v0/me/capabilities still returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
[ REQUEST ]
> URL: https://api-sandbox.uphold.com/v0/me/capabilities
> Method: GET
[19872:17836:0718/170657.642:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
> Url: https://api-sandbox.uphold.com/v0/me/capabilities
> Result: Success
> HTTP Code: 200
> Body: [  
 {    
 "category": "permissions",  
 "enabled": true,   
 "key": "receives",  
 "name": "Receives", 
 "requirements": [ "user-must-submit-customer-due-diligence" ], 
 "restrictions": [] 
 }, 
 {   
 "category": "permissions",   
 "enabled": false,   
 "key": "sends",  
 "name": "Sends",  
 "requirements": [],   
 "restrictions": [] 
 },   
 ]
  1. Confirmed modal message is shown
  2. Confirmed balance not displayed on rewards page or panel
  3. Confirmed status was as expected on brave://rewards-internals (still NOT CONNECTED)
Example Example
image image
Case 7 - Insufficient capabilities, receives=2, sends=1 with requirements - PASSED

Scenario 1 - Clean profile - PASSED

  1. Configured a Charles Proxy rule for the body of /v0/me/capabilities as per Implements Uphold /capabilities spec change. brave-core#14057 (comment), ensure rule is running
  2. Launched with a clean profile and staging env
  3. Enabled Rewards and linked Uphold account
  4. Confirmed /v0/me/capabilities was overwritten per the Charles Proxy rule as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
[ REQUEST ]
> URL: https://api-sandbox.uphold.com/v0/me/capabilities
> Method: GET
[19152:960:0718/171329.391:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
> Url: https://api-sandbox.uphold.com/v0/me/capabilities
> Result: Success
> HTTP Code: 200
> Body: [   
  {    
  "category": "permissions",  
  "enabled": false,   
  "key": "receives",  
  "name": "Receives", 
  "requirements": [], 
  "restrictions": [] 
  },  
  {    
  "category": "permissions",  
  "enabled": true, 
  "key": "sends",  
  "name": "Sends",  
  "requirements": [ "user-must-submit-customer-due-diligence" ],  
  "restrictions": [] 
  }, 

]
  1. Confirmed message displayed on brave://rewards page
  2. Confirmed no notification on BAT logo in URL bar
  3. Confirmed balance not shown on brave://rewards page or panel
  4. Confirmed status was as expected on brave://rewards-internals
Example Example
image image

Scenario 2 - Upgrade profile - on brave://rewards page prior to Upgrade - PASSED

  1. Using same Charles Proxy rule from "Clean Profile" case for this scenario, launched 1.41.x with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account
  3. Confirmed /v0/me/capabilities returned as expected for this case per Charles Proxy rule written as per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  4. Confirm unable to verify wallet due to "sends" or "receives" being false (implemented with previously with Implement error modal if user does not have receives OR sends capabilities on Uphold #22508)
  • modal with message is shown
  • no balance displayed on rewards page or panel
  1. Ensured brave://rewards page was active tab
  2. Closed 1.41.x
  3. "Upgraded" version (renamed profile) and Launched with upgraded version
  4. Confirmed status was as expected on brave://rewards-internals (still NOT CONNECTED)
  5. Attempt to link account again (with Charles Proxy still running the rewrite rule)
  6. Confirmed /v0/me/capabilities still returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
[ REQUEST ]
> URL: https://api-sandbox.uphold.com/v0/me/capabilities
> Method: GET
[22208:11276:0718/172017.541:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
> Url: https://api-sandbox.uphold.com/v0/me/capabilities
> Result: Success
> HTTP Code: 200
> Body: [  
 {   
 "category": "permissions",    
 "enabled": false, 
 "key": "receives",  
 "name": "Receives", 
 "requirements": [],  
 "restrictions": []  
 },  
 { 
 "category": "permissions", 
 "enabled": true, 
 "key": "sends",  
 "name": "Sends", 
 "requirements": [ "user-must-submit-customer-due-diligence" ], 
 "restrictions": [] 
 },  
]
  1. Confirmed modal message is shown
  2. Confirmed balance not displayed on rewards page or panel
  3. Confirmed status was as expected on brave://rewards-internals (still NOT CONNECTED)
Example Example
image image

Scenario 3 - Upgrade profile - brave://rewards page not open prior to Upgrade - PASSED

  1. Using same Charles Proxy rule from "Clean Profile" case for this scenario, launched 1.41.x with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account
  3. Confirmed /v0/me/capabilities returned as expected for this case per Charles Proxy rule written as per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  4. Confirm unable to verify wallet due to "sends" or "receives" being false (implemented with previously with Implement error modal if user does not have receives OR sends capabilities on Uphold #22508)
  • modal with message is shown
  • no balance displayed on rewards page or panel
  1. Ensured brave://rewards page was not open
  2. Closed 1.41.x
  3. "Upgraded" version (renamed profile) and Launched with upgraded version
  4. Confirmed status was as expected on brave://rewards-internals (still NOT CONNECTED)
  5. Attempt to link account again (with Charles Proxy still running the rewrite rule)
  6. Confirmed /v0/me/capabilities still returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
[ REQUEST ]
> URL: https://api-sandbox.uphold.com/v0/me/capabilities
> Method: GET
[2648:5232:0718/172623.315:VERBOSE6:logging_util.cc(137)]
[ RESPONSE - OnRequest ]
> Url: https://api-sandbox.uphold.com/v0/me/capabilities
> Result: Success
> HTTP Code: 200
> Body: [  
{   
  "category": "permissions", 
  "enabled": false,   
  "key": "receives",  
  "name": "Receives",  
  "requirements": [],
  "restrictions": []  
 },  
 {   
  "category": "permissions",   
  "enabled": true,  
  "key": "sends",  
  "name": "Sends",    
  "requirements": [ "user-must-submit-customer-due-diligence" ], 
  "restrictions": []  
 },   
]
  1. Confirmed modal message is shown
  2. Confirmed balance not displayed on rewards page or panel
  3. Confirmed status was as expected on brave://rewards-internals (still NOT CONNECTED)
Example Example
image image

@GeetaSarvadnya GeetaSarvadnya added QA Pass-Win64 and removed QA/In-Progress Indicates that QA is currently in progress for that particular issue labels Jul 19, 2022
@LaurenWags
Copy link
Member

For Android, I'd recommend testing Case 1, 2, 4 from #23849 (comment). Spot checking 3, 5, 6, 7 if there's time will be sufficient.

@Uni-verse Uni-verse added the QA/In-Progress Indicates that QA is currently in progress for that particular issue label Jul 28, 2022
@brave brave deleted a comment from Uni-verse Aug 2, 2022
@srirambv
Copy link
Contributor

srirambv commented Aug 2, 2022 •
edited
Loading

Verification in progress on Samsung Galaxy S21 using

Brave 1.42.81 Chromium: 104.0.5112.69 (Official Build) (64-bit)
Revision 7ce2902023c722af8564068e6b26e934b83fd774-refs/branch-heads/5112@{#1213}
OS Android 12; Build/SP1A.210812.016

Note - while running the below tests you may encounter known issue #16376 on the brave://rewards-internals page.

Case 1 - Sufficient capabilities - PASSED

Scenario 1 - Clean profile - PASSED

  1. Launched with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account that has sufficient capabilities
  3. Confirmed /v0/me/capabilities returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
:method: GET
:authority: api-sandbox.uphold.com
:scheme: https
:path: /v0/me/capabilities
sec-fetch-site: none
sec-fetch-mode: no-cors
sec-fetch-dest: empty
user-agent: Mozilla/5.0 (Linux; Android 12) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.5112.69 Safari/537.36
accept-encoding: gzip, deflate, br
accept-language: en-US,en;q=0.9,es-ES;q=0.8,es;q=0.7,ru-RU;q=0.6,ru;q=0.5,de-DE;q=0.4,de-AT;q=0.3,de;q=0.2,fr-FR;q=0.1,fr;q=0.1,es-US;q=0.1,ja-JP;q=0.1,ja;q=0.1

{
	"category": "permissions",
	"enabled": true,
	"key": "receives",
	"name": "Receives",
	"requirements": [],
	"restrictions": []
}, {
	"category": "permissions",
	"enabled": true,
	"key": "sends",
	"name": "Sends",
	"requirements": [],
	"restrictions": []
},
  1. Confirmed balance displayed on brave://rewards and panel
  2. Confirmed no notifications/messages about needing to complete additional requirements
Example Example
screenshot-1659137020982 screenshot-1659137052444

Scenario 2 - Upgrade profile - on brave://rewards page prior to Upgrade - PASSED

  1. Launched 1.41.x with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account that has sufficient capabilities
  3. Confirmed /v0/me/capabilities returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  4. Confirmed balance displayed on brave://rewards and panel
  5. Ensured brave://rewards page was active tab
  6. Closed 1.41.x and "Upgraded" version (renamed profile)
  7. Launched with upgraded version
  8. Confirmed /v0/me/capabilities still returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
:method: GET
:authority: api-sandbox.uphold.com
:scheme: https
:path: /v0/me/capabilities
sec-fetch-site: none
sec-fetch-mode: no-cors
sec-fetch-dest: empty
user-agent: Mozilla/5.0 (Linux; Android 12) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.5112.69 Mobile Safari/537.36
accept-encoding: gzip, deflate, br
accept-language: en-US,en;q=0.9,es-MX;q=0.8,es;q=0.7,de-AT;q=0.6,de;q=0.5,pt-BR;q=0.4,pt;q=0.3,de-DE;q=0.2,en-GB;q=0.1,ru-RU;q=0.1,ru;q=0.1,es-US;q=0.1,ja-JP;q=0.1,ja;q=0.1,pt-PT;q=0.1,en-CA;q=0.1,fr-FR;q=0.1,fr;q=0.1,en-DE;q=0.1


{
	"category": "permissions",
	"enabled": true,
	"key": "receives",
	"name": "Receives",
	"requirements": [],
	"restrictions": []
}, {
	"category": "permissions",
	"enabled": true,
	"key": "sends",
	"name": "Sends",
	"requirements": [],
	"restrictions": []
},

............
  1. Confirmed balance displayed on brave://rewards and panel
  2. Confirmed no notifications/messages about needing to complete additional requirements

Scenario 3 - Upgrade profile - brave://rewards page is not open prior to Upgrade - PASSED

  1. Launched 1.41.x with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account that has sufficient capabilities
  3. Confirmed /v0/me/capabilities returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  4. Confirmed balance displayed on brave://rewards and panel
  5. Ensured brave://rewards page was not open
  6. Closed 1.41.x and "Upgraded" version (renamed profile)
  7. Launched with upgraded version
  8. Confirmed /v0/me/capabilities still returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
:method: GET
:authority: api-sandbox.uphold.com
:scheme: https
:path: /v0/me/capabilities
sec-fetch-site: none
sec-fetch-mode: no-cors
sec-fetch-dest: empty
user-agent: Mozilla/5.0 (Linux; Android 12) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/104.0.5112.69 Mobile Safari/537.36
accept-encoding: gzip, deflate, br
accept-language: en-US,en;q=0.9,es-MX;q=0.8,es;q=0.7,de-AT;q=0.6,de;q=0.5,pt-BR;q=0.4,pt;q=0.3,de-DE;q=0.2,en-GB;q=0.1,ru-RU;q=0.1,ru;q=0.1,es-US;q=0.1,ja-JP;q=0.1,ja;q=0.1,pt-PT;q=0.1,en-CA;q=0.1,fr-FR;q=0.1,fr;q=0.1,en-DE;q=0.1

 {
	"category": "permissions",
	"enabled": true,
	"key": "receives",
	"name": "Receives",
	"requirements": [],
	"restrictions": []
}, {
	"category": "permissions",
	"enabled": true,
	"key": "sends",
	"name": "Sends",
	"requirements": [],
	"restrictions": []
}

............
  1. Confirmed balance displayed on panel
  2. Confirmed no notifications/messages about needing to complete additional requirements
Case 2 - Insufficient capabilities, receives=1 with requirements - IN PROGRESS

@GeetaSarvadnya
Copy link

GeetaSarvadnya commented Aug 2, 2022 •
edited
Loading

Verification PASSED on Samsung Galaxy Tab A7 version 11 running Bravemonoarm64.apk_1.42.85

Case 3 - Insufficient capabilities, receives=2 - PASSED

Scenario 1 - Clean profile - PASSED

  1. Configured a Charles Proxy rule for the body of /v0/me/capabilities as per Implements Uphold /capabilities spec change. brave-core#14057 (comment), ensure rule is running
  2. Launched with a clean profile and staging env
  3. Enabled Rewards and linked Uphold account
  4. Confirmed /v0/me/capabilities was overwritten per the Charles Proxy rule as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  5. Confirmed message displayed on brave://rewards page
  6. Confirmed no notification on BAT logo in URL bar
  7. Confirmed balance not shown on brave://rewards page or panel
  8. Confirmed status was as expected on brave://rewards-internals
Example Example
Screenshot_20220802-195445_Brave image

Scenario 2 - Upgrade profile - on brave://rewards page prior to Upgrade - PASSED

  1. Using same Charles Proxy rule from "Clean Profile" case for this scenario, launched 1.41.x with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account
  3. Confirmed /v0/me/capabilities returned as expected for this case per Charles Proxy rule written as per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  4. Confirm unable to verify wallet due to "sends" or "receives" being false (implemented with previously with Implement error modal if user does not have receives OR sends capabilities on Uphold #22508)
  • modal with message is shown
  • no balance displayed on rewards page or panel
  1. Ensured brave://rewards page was active tab
  2. Closed 1.41.x
  3. "Upgraded" version (renamed profile) and Launched with upgraded version
  4. Confirmed status was as expected on brave://rewards-internals (still NOT CONNECTED)
  5. Attempt to link account again (with Charles Proxy still running the rewrite rule)
  6. Confirmed /v0/me/capabilities still returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  7. Confirmed modal message is shown
  8. Confirmed balance not displayed on rewards page or panel
  9. Confirmed status was as expected on brave://rewards-internals (still NOT CONNECTED)
Example Example
Screenshot_20220802-202048_Brave image

Scenario 3 - Upgrade profile - brave://rewards page not open prior to Upgrade - PASSED

  1. Using same Charles Proxy rule from "Clean Profile" case for this scenario, launched 1.41.x with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account
  3. Confirmed /v0/me/capabilities returned as expected for this case per Charles Proxy rule written as per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  4. Confirm unable to verify wallet due to "sends" or "receives" being false (implemented with previously with Implement error modal if user does not have receives OR sends capabilities on Uphold #22508)
  • modal with message is shown
  • no balance displayed on rewards page or panel
  1. Ensured brave://rewards page was not open
  2. Closed 1.41.x
  3. "Upgraded" version (renamed profile) and Launched with upgraded version
  4. Confirmed status was as expected on brave://rewards-internals (still NOT CONNECTED)
  5. Attempt to link account again (with Charles Proxy still running the rewrite rule)
  6. Confirmed /v0/me/capabilities still returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
 [ REQUEST ]
    > URL: https://api-sandbox.uphold.com/v0/me/capabilities
    > Method: GET
2022-08-02 20:40:09.057 10587-10587/? V/chromium: [VERBOSE6:logging_util.cc(137)] 
    [ RESPONSE - OnRequest ]
    > Url: https://api-sandbox.uphold.com/v0/me/capabilities
    > Result: Success
    > HTTP Code: 200
    > Body: [
	
	{ 	
	
	"category": "permissions", 
	"enabled": false, 
	"key": "receives", 
	"name": "Receives", 
	"requirements": [], 
	"restrictions": [] 
	}, 
	{ 	
	
	"category": "permissions",
 	"enabled": true, 	
	"key": "sends", 	
	"name": "Sends", 
	"requirements": [],
 	"restrictions": [] 
	}, 
]
  1. Confirmed modal message is shown
  2. Confirmed balance not displayed on rewards page or panel
  3. Confirmed status was as expected on brave://rewards-internals (still NOT CONNECTED)
Example Example
Screenshot_20220802-204019_Brave image
Case 4 - Insufficient capabilities, sends=1 with requirements - PASSED

Scenario 1 - Clean profile - PASSED

  1. Configured a Charles Proxy rule for the body of /v0/me/capabilities as per Implements Uphold /capabilities spec change. brave-core#14057 (comment), ensure rule is running
  2. Launched with a clean profile and staging env
  3. Enabled Rewards and linked Uphold account
  4. Confirmed /v0/me/capabilities was overwritten per the Charles Proxy rule as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
 [ REQUEST ]
    > URL: https://api-sandbox.uphold.com/v0/me/capabilities
    > Method: GET
2022-08-02 20:50:21.602 16043-16043/? W/chromium: [WARNING:compositor_view.cc(342)] Child process died (type=6) pid=16605)
2022-08-02 20:50:21.981 16043-16043/? V/chromium: [VERBOSE6:logging_util.cc(137)] 
    [ RESPONSE - OnRequest ]
    > Url: https://api-sandbox.uphold.com/v0/me/capabilities
    > Result: Success
    > HTTP Code: 200
    > Body: [

	{ 
	"category": "permissions", 
	"enabled": true, 
	"key": "receives", 
	"name": "Receives", 
	"requirements": [], 
	"restrictions": [] 
	}, 
	{ 	
	"category": "permissions", 
	"enabled": true, 
	"key": "sends", 	
	"name": "Sends", 
	"requirements": ["user-must-submit-customer-due-diligence"], 
	"restrictions": [] 
	}, 
]
  1. Confirmed message displayed on brave://rewards page
  2. Confirmed no notification on BAT logo in URL bar
  3. Confirmed balance not shown on brave://rewards page or panel
  4. Confirmed status was as expected on brave://rewards-internals
Example Example
Screenshot_20220802-205032_Brave image

Scenario 2 - Upgrade profile - on brave://rewards page prior to Upgrade - PASSED

  1. Using same Charles Proxy rule from "Clean Profile" case for this scenario, launched 1.41.x with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account
  3. Confirmed balance displayed on brave://rewards and panel
  4. Confirmed /v0/me/capabilities returned as expected for this case per Charles Proxy rule written as per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  5. Ensured brave://rewards page was active tab
  6. Closed 1.41.x
  7. "Upgraded" version (renamed profile) and Launched with upgraded version
  8. Confirmed /v0/me/capabilities still returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  9. Confirmed modal and notification (on BAT logo) are shown
  10. Confirmed balance no longer displayed on rewards page or panel
  11. Confirmed status was as expected on brave://rewards-internals (VERIFIED --> NOT CONNECTED)
  12. Confirmed logs showed the below as per the PR:
[ REQUEST ]
    > URL: https://grant.rewards.bravesoftware.com/v3/wallet/uphold/4a090587-8718-40f2-9b77-5b99eef4a275/claim
    > Method: DEL
    > Content Type: application/json; charset=utf-8
    > Header digest: SHA-256=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=
    > Header signature: keyId="4a090587-8718-40f2-9b77-5b99eef4a275",algorithm="ed25519",headers="digest (request-target)",signature="IY4JJW325avbBt3MAjGkKbRTI9zWJuPlxY059Efp3xVgb3bLcjd/O2QKHyANN2DYSIGSvMupfepy59un1eCaCw=="
    > Header accept: application/json
2022-08-02 21:00:05.970 21823-21823/? V/chromium: [VERBOSE6:logging_util.cc(137)] 
    [ RESPONSE - OnRequest ]
    > Url: https://grant.rewards.bravesoftware.com/v3/wallet/uphold/4a090587-8718-40f2-9b77-5b99eef4a275/claim
    > Result: Success
    > HTTP Code: 200
    > Body: null
2022-08-02 21:00:05.978 21823-21823/? V/chromium: [VERBOSE1:uphold.cc(186)] Disconnecting wallet
Example Example Example
Screenshot_20220802-210015_Brave Screenshot_20220802-210046_Brave image

Scenario 3 - Upgrade profile - brave://rewards page is not open prior to Upgrade - PASSED

  1. Using same Charles Proxy rule from "Clean Profile" case for this scenario, launched 1.41.x with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account
  3. Confirmed balance displayed on brave://rewards and panel
  4. Confirmed /v0/me/capabilities returned as expected for this case per Charles Proxy rule written as per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  5. Ensured brave://rewards page was not open tab
  6. Closed 1.41.x
  7. "Upgraded" version (renamed profile) and Launched with upgraded version
  8. Confirmed /v0/me/capabilities still returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  9. Confirmed only notification (on BAT logo) is shown (no modal)
  10. Confirmed balance no longer displayed on rewards page or panel
  11. Confirmed status was as expected on brave://rewards-internals (VERIFIED --> NOT CONNECTED)
  12. Confirmed logs showed the below as per the PR:
[ REQUEST ]
    > URL: https://api-sandbox.uphold.com/v0/me/cards/4f157868-e243-4eab-bbea-e10318a3b971
    > Method: GET
2022-08-02 21:10:45.169 27067-27067/? V/chromium: [VERBOSE6:logging_util.cc(137)] 
    [ RESPONSE - OnRequest ]
    > Url: https://api-sandbox.uphold.com/v0/me/cards/4f157868-e243-4eab-bbea-e10318a3b971
    > Result: Success
    > HTTP Code: 200
    > Body: {"CreatedByApplicationId":"193a77cf-02e8-4e10-8127-8a1b5a8bfece","address":{"wire":"UH3AB23B52","ethereum":"0x4bA4437b75365530D07d537d8d9809BDD215c1Cf"},"available":"20.15","balance":"20.15","currency":"BAT","id":"4f157868-e243-4eab-bbea-e10318a3b971","label":"Brave Browser","lastTransactionAt":"2022-08-01T13:46:49.904Z","settings":{"position":1,"protected":false,"starred":true},"normalized":[{"available":"8.02","balance":"8.02","currency":"USD"}],"wire":[{"accountName":"Uphold Europe Limited","address":{"line1":"Tartu mnt 2","line2":"10145 Tallinn, Estonia"},"bic":"LHVBEE22","currency":"EUR","iban":"EE76 7700 7710 0159 0178","name":"AS LHV Pank"},{"accountName":"Uphold Europe Limited","accountNumber":"00000083","address":{"line1":"1 Angel Court","line2":"London, EC2R 7HJ"},"bic":"LHVBEE22","currency":"GBP","iban":"EE76 7700 7710 0159 0178","name":"AS LHV PANK UK BRANCH","sortCode":"040300"},{"accountName":"Uphold HQ, Inc.","accountNumber":"299007316","address":{"line1":"99 Park Avenue, Floor 4","line2":"New York, NY 10016"},"bic":"MCBEUS33","currency":"USD","name":"Metropolitan Commercial Bank","routingNumber":"026013356"}]}
2022-08-02 21:10:45.233 27067-27067/? V/chromium: [VERBOSE6:logging_util.cc(137)] 
    [ RESPONSE - OnRequest ]
    > Url: https://grant.rewards.bravesoftware.com/v3/wallet/uphold/882c7b78-f8c3-4ba7-8f38-c9f49ba712e3/claim
    > Result: Success
    > HTTP Code: 200
    > Body: null
2022-08-02 21:10:45.237 27067-27067/? V/chromium: [VERBOSE1:uphold.cc(186)] Disconnecting wallet
Example Example
Screenshot_20220802-211144_Brave image
Case 2 - Insufficient capabilities, receives=1 with requirements - PASSED

Scenario 1 - Clean profile - PASSED

  1. Configured a Charles Proxy rule for the body of /v0/me/capabilities as per Implements Uphold /capabilities spec change. brave-core#14057 (comment), ensure rule is running
  2. Launched with a clean profile and staging env
  3. Enabled Rewards and linked Uphold account
  4. Confirmed /v0/me/capabilities was overwritten per the Charles Proxy rule as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)

 [ RESPONSE - OnRequest ]
    > Url: https://api-sandbox.uphold.com/v0/me/capabilities
    > Result: Success
    > HTTP Code: 200
    > Body: [
	
	{ 	
	"category": "permissions",
 	"enabled": true, 
	"key": "receives", 
	"name": "Receives", 
	"requirements": ["user-must-submit-customer-due-diligence"], 
	"restrictions": [] 
	},
	{ 	
	"category": "permissions", 
	"enabled": true, 
	"key": "sends", 
	"name": "Sends", 
	"requirements": [], 
	"restrictions": [] 
	}, 
	
]
  1. Confirmed message displayed on brave://rewards page
  2. Confirmed no notification on BAT logo in URL bar
  3. Confirmed balance not shown on brave://rewards page or panel
  4. Confirmed status was as expected on brave://rewards-internals
Example Example
Screenshot_20220802-220951_Brave image

Scenario 2 - Upgrade profile - on brave://rewards page prior to Upgrade - PASSED

  1. Using same Charles Proxy rule from "Clean Profile" case for this scenario, launched 1.41.x with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account
  3. Confirmed balance displayed on brave://rewards and panel
  4. Confirmed /v0/me/capabilities returned as expected for this case per Charles Proxy rule written as per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  5. Ensured brave://rewards page was active tab
  6. Closed 1.41.x
  7. "Upgraded" version (renamed profile) and Launched with upgraded version
  8. Confirmed /v0/me/capabilities still returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
[ RESPONSE - OnRequest ]
    > Url: https://api-sandbox.uphold.com/v0/me/capabilities
    > Result: Success
    > HTTP Code: 200
    > Body: [
	
	{ 	
	"category": "permissions",
 	"enabled": true, 
	"key": "receives", 
	"name": "Receives", 
	"requirements": ["user-must-submit-customer-due-diligence"],
 	"restrictions": [] 
	}, 
	{ 	
	"category": "permissions", 	
	"enabled": true, 	
	"key": "sends", 
	"name": "Sends", 
	"requirements": [], 
	"restrictions": [] 
	},
  1. Confirmed modal and notification (on BAT logo) are shown
  2. Confirmed balance no longer displayed on rewards page or panel
  3. Confirmed status was as expected on brave://rewards-internals (VERIFIED --> NOT CONNECTED)
  4. Confirmed logs showed the below as per the PR:
 [ REQUEST ]
    > URL: https://grant.rewards.bravesoftware.com/v3/wallet/uphold/37692c06-6534-420b-b7c0-d5bb5969c394/claim
    > Method: DEL
    > Content Type: application/json; charset=utf-8
    > Header digest: SHA-256=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=
    > Header signature: keyId="37692c06-6534-420b-b7c0-d5bb5969c394",algorithm="ed25519",headers="digest (request-target)",signature="uuKpmRR8Mgx7OdTgmGpWbgQGu1YcfGetJTLZiT6ZhkCKo7PWI0RTQmcRQhJdtb7dMQ1I88N/3tkw5KnKlWzpBw=="
    > Header accept: application/json
2022-08-02 22:20:43.778 9947-9947/? V/chromium: [VERBOSE5:ledger_impl.cc(114)] 
    [ REQUEST ]
    > URL: https://api-sandbox.uphold.com/v0/me/capabilities
    > Method: GET
2022-08-02 22:20:43.956 9947-9947/? V/chromium: [VERBOSE6:logging_util.cc(137)] 
    [ RESPONSE - OnRequest ]
    > Url: https://grant.rewards.bravesoftware.com/v3/wallet/uphold/37692c06-6534-420b-b7c0-d5bb5969c394/claim
    > Result: Success
    > HTTP Code: 200
    > Body: null
2022-08-02 22:20:43.959 9947-9947/? V/chromium: [VERBOSE1:uphold.cc(186)] Disconnecting wallet
Example Example Example
Screenshot_20220802-222050_Brave Screenshot_20220802-222121_Brave image

Scenario 3 - Upgrade profile - brave://rewards page is not open prior to Upgrade - PASSED

  1. Using same Charles Proxy rule from "Clean Profile" case for this scenario, launched 1.41.x with a clean profile and staging env
  2. Enabled Rewards and verify w/ Uphold account
  3. Confirmed balance displayed on brave://rewards and panel
  4. Confirmed /v0/me/capabilities returned as expected for this case per Charles Proxy rule written as per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  5. Ensured brave://rewards page was not open tab
  6. Closed 1.41.x
  7. "Upgraded" version (renamed profile) and Launched with upgraded version
  8. Confirmed /v0/me/capabilities still returned as expected for this case per Implements Uphold /capabilities spec change. brave-core#14057 (comment)
  [ REQUEST ]
    > URL: https://api-sandbox.uphold.com/v0/me/capabilities
    > Method: GET
2022-08-02 22:33:40.869 14433-14433/? V/chromium: [VERBOSE6:logging_util.cc(137)] 
    [ RESPONSE - OnRequest ]
    > Url: https://api-sandbox.uphold.com/v0/me/capabilities
    > Result: Success
    > HTTP Code: 200
    > Body: [
	{ 	
	"category": "permissions", 
	"enabled": true, 	
	"key": "receives", 
	"name": "Receives", 
	"requirements": ["user-must-submit-customer-due-diligence"], 
	"restrictions": [] 
	},
	{ 	
	"category": "permissions", 
	"enabled": true, 
	"key": "sends", 
	"name": "Sends", 
	"requirements": [], 
	"restrictions": [] 
	}, 
	
]
  1. Confirmed only notification (on BAT logo) is shown (no modal)
  2. Confirmed balance no longer displayed on rewards page or panel
  3. Confirmed status was as expected on brave://rewards-internals (VERIFIED --> NOT CONNECTED)
  4. Confirmed logs showed the below as per the PR:
 [ REQUEST ]
    > URL: https://grant.rewards.bravesoftware.com/v3/wallet/uphold/7b32a420-441b-4a4d-9d6b-49352d9375df/claim
    > Method: DEL
    > Content Type: application/json; charset=utf-8
    > Header digest: SHA-256=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=
    > Header signature: keyId="7b32a420-441b-4a4d-9d6b-49352d9375df",algorithm="ed25519",headers="digest (request-target)",signature="KCqlSIUjHdSds/Gk1ZuSQTgk8hIzhGWfBtdOStA4qg2ZQzEHAzV7deL1hk6bHLcrZnjVA8y7j6wc27/5m9U5AA=="
    > Header accept: application/json
2022-08-02 22:35:26.564 15919-15919/? V/chromium: [VERBOSE5:ledger_impl.cc(114)] 
    [ REQUEST ]
    > URL: https://api-sandbox.uphold.com/v0/me/cards/4f157868-e243-4eab-bbea-e10318a3b971
    > Method: GET
2022-08-02 22:35:27.076 15919-15919/? V/chromium: [VERBOSE6:logging_util.cc(137)] 
    [ RESPONSE - OnRequest ]
    > Url: https://api-sandbox.uphold.com/v0/me/cards/4f157868-e243-4eab-bbea-e10318a3b971
    > Result: Success
    > HTTP Code: 200
    > Body: {"CreatedByApplicationId":"193a77cf-02e8-4e10-8127-8a1b5a8bfece","address":{"wire":"UH3AB23B52","ethereum":"0x4bA4437b75365530D07d537d8d9809BDD215c1Cf"},"available":"20.15","balance":"20.15","currency":"BAT","id":"4f157868-e243-4eab-bbea-e10318a3b971","label":"Brave Browser","lastTransactionAt":"2022-08-01T13:46:49.904Z","settings":{"position":1,"protected":false,"starred":true},"normalized":[{"available":"8.27","balance":"8.27","currency":"USD"}],"wire":[{"accountName":"Uphold Europe Limited","address":{"line1":"Tartu mnt 2","line2":"10145 Tallinn, Estonia"},"bic":"LHVBEE22","currency":"EUR","iban":"EE76 7700 7710 0159 0178","name":"AS LHV Pank"},{"accountName":"Uphold Europe Limited","accountNumber":"00000083","address":{"line1":"1 Angel Court","line2":"London, EC2R 7HJ"},"bic":"LHVBEE22","currency":"GBP","iban":"EE76 7700 7710 0159 0178","name":"AS LHV PANK UK BRANCH","sortCode":"040300"},{"accountName":"Uphold HQ, Inc.","accountNumber":"299007316","address":{"line1":"99 Park Avenue, Floor 4","line2":"New York, NY 10016"},"bic":"MCBEUS33","currency":"USD","name":"Metropolitan Commercial Bank","routingNumber":"026013356"}]}
2022-08-02 22:35:27.459 15919-15919/? V/chromium: [VERBOSE6:logging_util.cc(137)] 
    [ RESPONSE - OnRequest ]
    > Url: https://grant.rewards.bravesoftware.com/v3/wallet/uphold/7b32a420-441b-4a4d-9d6b-49352d9375df/claim
    > Result: Success
    > HTTP Code: 200
    > Body: null
2022-08-02 22:35:27.465 15919-15919/? V/chromium: [VERBOSE1:uphold.cc(186)] Disconnecting wallet
Example Example
Screenshot_20220802-223540_Brave image

@LaurenWags LaurenWags added QA Pass - Android Tab and removed QA/In-Progress Indicates that QA is currently in progress for that particular issue labels Aug 2, 2022
@LaurenWags LaurenWags mentioned this issue Aug 9, 2022
Closed
@LaurenWags LaurenWags mentioned this issue Dec 12, 2022
Closed
@LaurenWags LaurenWags mentioned this issue Jan 11, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@szilardszaloki szilardszaloki

Labels
feature/rewards OS/Android Fixes related to Android browser functionality OS/Desktop priority/P1 A very extremely bad problem. We might push a hotfix for it. QA Pass - Android Tab QA Pass-Win64 QA/Yes release-notes/exclude
Projects
None yet
Milestone
1.42.x - Release
Development

Successfully merging a pull request may close this issue.

Implements Uphold /capabilities spec change. brave/brave-core
8 participants
@kjozwiak @szilardszaloki @Miyayes @srirambv @Uni-verse @LaurenWags @GeetaSarvadnya @brave-builds