Currently they have just one option for storing a merchant token for a custom payment solution. We have a scenario where a single corporation needs multiple account settings based off of locations. For example, say a single corp has 4 locations and each location needs a specific merchant account token. We need options to be able to store and use unlimited number of sub accounts.

Talk with Brandon to get details. But the idea is, we keep it as a default of 1 unless they need more. If they need more, we provide a selector where they could put a counter (say 4 or whatever). We then show them that many settings. The web page id stuff allows for multiple optional fields. We could either use those or we could make a note that we have to go external to custom JSON storage (to go deeper).

There is a target date of end of day on Wednesday 4/8/20.

As a side note, Brandon also has a new file that has all of the Hypur error messages (in an array) that would be awesome if we could include that in the existing logic.