# Facemaps

Facemaps are inherence-based (biometric) SCA challenge factors that use FaceTec's 3D face recognition technology.
Facemaps should be exported from your FaceTec server using their SDK's export API. Use Wise's [FaceTec public key](/api-reference/legacy/facetec/facetecpublickeyget) to encrypt the facemap during export.

 - [POST /v2/profiles/{profileId}/facemaps](https://docs.wise.com/api-reference/legacy/sca-facemaps/scafacemapcreate.md): Creates a new facemap factor used to resolve a SCA inherence challenge type. A facemap should be exported from your FaceTec server using the SDK's [export API](https://dev.facetec.com/api-guide#export
 - [DELETE /v2/profiles/{profileId}/facemaps](https://docs.wise.com/api-reference/legacy/sca-facemaps/scafacemapdelete.md): Deletes a facemap associated to a profile. To update a facemap for a profile, use this endpoint followed by [Create a facemap](/api-reference/legacy/sca-facemaps/scafacemapcreate). This operation is i
 - [POST /v2/profiles/{profileId}/facemaps/verify](https://docs.wise.com/api-reference/legacy/sca-facemaps/scafacemapverify.md): Verifies a facemap challenge when calling a SCA-secured endpoint. Make sure to [create a facemap](/api-reference/legacy/sca-facemaps/scafacemapcreate) before using this endpoint. A facemap should be e
 - [POST /v1/one-time-token/facemap/verify](https://docs.wise.com/api-reference/legacy/sca-facemaps/ottfacemapverify.md): To clear a **FACE_MAP** challenge listed in a OTT. Notes: 1. User is required to [enrol facemap](/api-reference/legacy/user-security/usersecurityfacemapenrol) before the verification can be successful