My app allows a user to create connections to multiple Clover accounts (Merchant IDs) for the purpose of aggregating reports across devices/locations.
A problem occurs in the OAuth process when a user is already logged into Clover for a Merchant ID but wants to create a connection to a different Merchant ID. In this scenario, Clover does NOT prompt the user to sign in during the OAuth process. The result is a connection to the wrong Merchant ID.
Some OAuth implementations (like Google's API) support the "&prompt=login" parameter in the OAuth authorization request (/oauth/v2/authorize for Clover), which requires the user to sign in even if they already are. However, this parameter does not appear to work for Clover.
Are there any workarounds for this issue? It doesn't appear possible to "force" a Clover logout before starting the OAuth process or to initiate the OAuth process in an "Incognito" mode.
Any ideas are welcome. Thanks in advance.