Creates a challenge for the user to sign for the mobile biometrics flow.
Security
ClientAccessToken
One of:
Identifier of the device from which the authentication request originates
Flat object that contains the data that your customer should approve for a transaction signing or custom approval flow. It can contain up to 10 keys, and only alphanumeric characters, underscores, hyphens, and periods. It will be returned as a claim in the ID token upon successful authentication.
Example:
{ "transaction_id": "eFII2y40uB9hQ98nXt3tc1IHkRt8GrRZiqZuRn_59wT", "sum": "200" }
User identifier, which may correspond to the user's email, phone number, username, or user ID. The type of identifier should be specified as the identifier_type.
- Sandbox environmenthttps://api.sbx.transmitsecurity.io/cis/v1/auth/mobile-biometrics/start
- US production environmenthttps://api.transmitsecurity.io/cis/v1/auth/mobile-biometrics/start
- EU production environmenthttps://api.eu.transmitsecurity.io/cis/v1/auth/mobile-biometrics/start
- CA production environmenthttps://api.ca.transmitsecurity.io/cis/v1/auth/mobile-biometrics/start
- AU production environmenthttps://api.au.transmitsecurity.io/cis/v1/auth/mobile-biometrics/start
- JP production environmenthttps://api.gasne1-ts01.transmitsecurity.io/cis/v1/auth/mobile-biometrics/start
- ApiNativeMobileBiometricsStartWithIdentifierRequestDto
- ApiNativeMobileBiometricsStartWithUserIdRequestDto
curl -i -X POST \
https://api.sbx.transmitsecurity.io/cis/v1/auth/mobile-biometrics/start \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"device_id": "string",
"approval_data": {
"transaction_id": "eFII2y40uB9hQ98nXt3tc1IHkRt8GrRZiqZuRn_59wT",
"sum": "200"
},
"timeout": 600,
"identifier": "string",
"identifier_type": "string"
}'