Confirm transactions using Hanko Authenticator

The process for confirming transactions with the Hanko Authenticator is essentially the same as for the regular authentication process. The main difference between the two is that when initializing the request you need to supply a request body with an additional transaction attribute. Its value is a transaction text that is part of the request metadata displayed in the confirmation prompt during out-of-band communication. It also becomes part of the challenge issued by the FIDO server and hence the signature created in the course of the authentication process.

curl -X POST "{API_URL}/v1/uaf/requests" \
-H 'Authorization:secret pasteYourApiKeyHere' \
-H 'Content-Type: application/json' \
-d '{"operation": "AUTH", "username":"example@example.com", "userId":"exampleId", "transaction": "Transfer $100 to Mike?" }'

http POST {API_URL}/v1/uaf/requests \
 'Authorization:secret pasteYourApiKeySecretHere' \
 'operation=AUTH' \
 'username=example@example.com' \
 'userId=exampleId' \
 'transaction=Transfer $100 to Mike?'

Authentication De-registration

Getting started

Quickstarts

Guides

SDKs & Plugins

API Reference

Confirm transactions using Hanko Authenticator