-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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.
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
Uphold linking always creates a new card #35445
Comments
Adding |
Thanks for running through #35445 (comment) to make sure everything is working as expected via |
Verification PASSED on
Case 1 - Possible pre-req: if Uphold is sending
Case 2 -
Case 3 - Initial connection with pre-req: have Charles Proxy running, but do not have rewrite rule for
|
Verified with
Case 1 - Possible pre-req: if Uphold is sending
Case 2 -
Case 3 - Initial connection with pre-req: have Charles Proxy running, but do not have rewrite rule for
|
Verification PASSED on Case 1 - Possible pre-req: if Uphold is sending
Case 2 -
Case 3 - Initial connection with pre-req: have Charles Proxy running, but do not have rewrite rule for
|
Uphold is now returning an HTTP status code of 206 on success from the
/v0/me/cards?q=currency:BAT
. This endpoint is used to determine if the user has an existing "Brave Browser" card. If the user has an existing card, then that card is used for Rewards operations. Otherwise, a new card is created with the label "Brave Browser".Uphold is now returning 206 from this endpoint, which the Rewards client does not recognize.
The text was updated successfully, but these errors were encountered: