SMS Verify API - SMPP TLVs
These TLVs are supported only when using SMPP to query Telesign SMS Verify API.
If you haven't already, first review SMPP protocol to learn our general SMPP requirements before reading this page.
These TLVS are related to Verify Plus, the Telesign product which screens out potentially fraud-related SMS Verify transactions using a risk recommendation before sending the user a verification SMS. Ask the Telesign Customer Support Team if you would like to enable this feature for SMS Verify.
phone_type
The type of the phone number in the request. May be included in the deliver_sm PDU sent in response to SMS Verify requests when Verify Plus is enabled.
| Field | Octets Size | Type | Description |
|---|---|---|---|
| Parameter Tag | 2 | Integer | 0x1407 |
| Length | 2 | Integer | Length of Value field in octets |
| Value | 2 | Octet-String | Contains these sub-fields: • code (phone type code)• description (the phone type)Example: "code:2; description:MOBILE" |
risk_score
The risk recommendation and associated data for the phone number in the request. May be included in the deliver_sm PDU sent in response to SMS Verify requests when Verify Plus is enabled.
| Field | Octets Size | Type | Description |
|---|---|---|---|
| Parameter Tag | 2 | Integer | 0x1408 |
| Length | 2 | Integer | Length of Value field in octets |
| Value | 2 | C-Octet String | Contains these sub-fields: • level (a description of the severity of the risk)• score (the risk recommendation itself)• recommendation (the action TeleSign recommends you take based on the risk recommendation) Example: "level:low; score:1; recommendation:allow" |
risk_insights
Contains reason code sub-fields with additional info related to the risk recommendation. Intelligence - Insights reason code mappings provides the meaning of these reason codes.
| Field | Octets Size | Type | Description |
|---|---|---|---|
| Parameter Tag | 2 | Integer | 0x140A |
| Length | 2 | Integer | Length of Value field in octets |
| Value | 2 | C-Octet String | Contains these sub-fields: • status (The processing status of the risk insights package for this request.)• category (Reason codes related to the category of the phone number.)• a2p (Reason codes specific to application-to-person communication (A2P). These are automated communications sent to a human, like verification codes, appointment reminders, etc.) • p2p (Reason codes specific to person-to-person communication (P2P). This is two-way communication between two humans, like one friend texting another.) • numberType (Reason codes related to the phone number’s type.) Example: "status:800; category:[10040]; a2p:[22001, 20012, 20101]; p2p:[30201]; numberType:[40004, 40013]" |
numbering
The original phone number from the request, along with some additional details.
| Field | Size Octets | Type | Description |
|---|---|---|---|
| Parameter Tag | 2 | Integer | 0x1409 |
| Length | 2 | Integer | Length of Value field in octets |
| Value | 2 | C-Octet String | Contains these sub-fields: • phone_number (the phone number without the country dialing code)• min_length (the minimum number of digits allowed for phone numbers with this country dialing code)• max_length (the maximum number of digits allowed for phone numbers with this country dialing code)• country_code (a 1, 2, or 3-digit number representing the country dialing code for this phone number) Example: "phone_number:5558675309; min_length:5; max_length:15; country_code:1" |
Updated about 1 year ago