Regarding returning to the register: I've discovered that my intervening activity was implicitly activating my main activity when it finished. Now in the manifest I set the intervening activity's taskAffinity to "", so android doesn't activate that main activity and control returns to Register as it should. Like this:
android:taskAffinity=""
Now I just need to know whether it's kosher for me to handle ACTION_PAYMENT_PROCESSED in this way, or whether there's a better option.
I've tried responding to ACTION_REQUEST_PAYMENT_REMOTE_VIEWS with ACTION_UPDATE_PAYMENT_REMOTE_VIEWS, but I don't ever see my view and those intents are essentially undocumented in the Clover api and unmentioned in these forums. I assume they're there for some Big Vendor that Clover is catering to.
1 Person is following this question.