Verify
Service that validates the user's identity and generates a verification token for Integration with Previred.
This service validates all Onboarding results and generates a secure token that is used to build the verification URL shared with Previred.
Prerequisites
Before calling this service, make sure the user has completed the Onboarding process with valid results:
facialAuthenticationResult = 3(Successful facial authentication)passiveLivenessResult = 3(liveness check passed)documentValidation = 9001(Document validation approved)
Endpoint
POST /services/previred/{serviceTransactionId}/verifyHeaders
x-api-key
string
Yes
Access authorization API Key.
Path parameters
serviceTransactionId
string
Yes
Unique transaction identifier for the transfer process.
Request body
Content-Type: application/json
Parameters
scanReference
string
Yes
Reference identifier of the Onboarding process that contains the identity validation results.
Request example
Responses
200 Success
Response parameters
token
string
Verification token to build the verification URL shared with Previred.
Response example
400 Bad Request
401 Unauthorized
403 Forbidden
404 Not Found
502 Bad Gateway
504 Gateway Timeout
Sending verification evidence to Previred
Once the token is obtained, the AFP must send the url_verificacion to Previred as proof of validation.
Verification URL format
Call to Previred - Token Request
Headers:
Content-Type
string
Yes
application/json
Authorization
string
Yes
Basic {authToken}
Request example:
Response example:
Call to Previred - Get token
Request example:
Response example:
UUID format for Previred
Previred imposes a 30-character limit on codigo_verificacion. UUIDs (36 characters) are converted to URL-safe Base64 without padding.
UUID to URL-safe Base64 conversion
Example:
3994d0f4-77c2-4079-8fd3-ccd14e90f909
OTlEbw93wkCeNMzNF5D5CQ
Implementation in Go:
Last updated