Verification is our first "use-case" API. We’re not just passing on Open Banking data (AIS), we’re adding value with our name-matching engine which allows customers to accurately verify their users, without having to process streams of raw bank data.
How does it work?
We redirect users to their banking app where they confirm account ownership using their fingerprint or Face ID. In the background, we crosscheck the user’s name with their bank records to make sure the names match.
TrueLayer’s Verification Engine provides the merchant with one of the following results in real-time:
- Match (True)
- No Match (False)
- No Account Holder Name found
A match result, along with the user’s authenticated bank details, gives the merchant confidence that the account and account holder are verified and authentic.
Example of the report our customer receives:
export ACCESS_TOKEN="users-access-token"
export name="Will Johnson"
curl --location --request POST 'https://api.truelayer.com/verification/v1/verify' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer $ACCESS_TOKEN' \
--data-raw '{"name": "'"$name"'"}'
Response
{
"verified": true,
"account_holder_name": "William Johnson",
"match_score": 89,
"report": [
{
"verifiable": true,
"currency": "GBP",
"provider_id": "ob-monzo",
"account_type": "CURRENT",
"account_holders": [
{
"name": "William Johnson",
"verified": true,
"match_score": 89
}
],
"display_name": "1st Account",
"iban": "GB70MONZ03952941110044",
"swift_bic": "MONZGB26",
"account_number": "53920022",
"sort_code": "04-11-34"
},
{
"verifiable": false,
"faliure_description": "Credit cards cannot be verified by this service.",
"failure_code": "CREDIT_CARD",
"provider_id": "ob-monzo",
"account_type": "CREDIT_CARD",
"display_name": "Gold card"
}
]
}
More
Read more about our Verification API in our documentation.
Comments
0 comments
Please sign in to leave a comment.