ID

8bb26115-2c37-4358-bc31-3a8745eac58c

MMPY-296 Limit Panda Blue in Dropdown

- source :: https://multimediallc.atlassian.net/browse/MMPY-296

- tags :: Falcon Nest Project Falcon Talon Project Falcon Talon Project Story

- epic :: MMPY-276 API Validations for all Payout Methods to add accounts

- sprint :: MM Sprint 28

- status :: Status - Complete

DONE Figure out the best way to get and store PandaBlue whitelist info

ID

56e726e4-344a-86f1-f67e-7536435a2082

DONE Add validation check for PandaBlue whitelist to payout method list endpoint

ID

a8eda229-1d5a-a792-8c34-da12426cd10c

TODO Add tests for PandaBlue whitelist to payout method list endpoint

Background

Panda Blue is currently only offered to users who have been whitelisted.

We receive this whitelisting in the user endpoint. During the panda blue

release, I would like to get rid of this white listing and adjust processes that

are barriers for allowing anyone to have access.

I recommend using a redis key to store or directly hit the CB endpoint to get

the panda blue eligibility instead of a data migration, as it is a short lived

feature. (Open to feedback and commentary on this)

Requirements

GIVEN A user’s address is in a country we currently offer PandaBlue for (current functionality)

AND the user’s info from CB also indicates they are in the PandaBlue whitelist

WHEN They load the selection of payment options

THEN Panda Blue should show in the list of options.

Requirement

GIVEN A user’s address is in a country we currently offer PandaBlue for (current functionality)

AND the user’s info from CB DOES NOT indicates they are in the PandaBlue whitelist

WHEN They load the selection of payment options

THEN Panda Blue should NOT show in the list of options.