Expose setDeviceEngagmement publicly #1495
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow for device engagement data obtained from an external source to be injected into the verification flow.
We specifically use this to add verification functionality to Android devices with only payment card NFC / without proper Android NFC. A proprietary SDK is used to retrieve the engagement data. The now-public method here is used to feed it into multipaz and continue the verification flow.
For reference, this is sample code how we're utilizing this method.
Wasn't sure if a unit test was required since this is just making an existing, tested code path public. However, I added a simple one.
Thank you for your consideration.
Testing
See unit test.
We also have this working end-end with our payment NFC hardware / SDK, which I can't reasonably demonstrate unfortunately.