The Line Status Manager module provides us with fraud reports related to telephone lines, which have been registered by associated customers.
The events that are contemplated are:
Through authentication Basic
ℹ️ In the case of using Basic Authentication, the final point of the validator to be used must be requested from Masiv.
URL Method POST: /changesimcard
Field | Data type | Mandatory? | Description |
---|---|---|---|
Recipient |
String |
Sí | Telephone number. |
ExpirationDay |
Number |
Si | Number of days the record stays in DB. |
EntityCategority |
String |
No | Entity class that reports. Ahem. Bank, Operator, Entity. |
OldIdSimCard |
String |
No | Characters that identify the SimCard |
CurrentIdSimCard |
String |
No | characters that identify the SimCar |
MetaData |
String |
No | Additional data. |
{
"Recipient": "string",
"ExpirationDays": "number",
"EntityCategory": "string",
"OldIdSimCard": "string",
"CurrentIdSimCard": "string",
"MetaData": "string"
}
URL Method POST: /fraud
Field | Data type | Mandatory? | Description |
---|---|---|---|
Recipient |
String |
Sí | Telephone number. |
IdClient |
String |
Si | Client identifier on the platform Masiv. |
ExpirationDay |
Number |
Si | Number of days the record stays in DB. |
EntityCategority |
String |
No | Entity class that reports. Ahem. Bank, Operator, Entity. |
IdSimCard |
String |
No | Characters that identify the SimCard. |
FraudReason |
String |
No | Reason why report the fraud. |
MetaData |
String |
No | Additional data. |
{
"Recipient": "string",
"IdClient": "string",
"ExpirationDays": "number",
"EntityCategory": "string",
"IdSimCard": "string",
"FraudReason": "string",
"MetaData": "string"
}
Note: For the insertion of Fraud data, a list must be made with the usual frauds that a Banking-type client can choose, to carry out a enabling these fields on the system or you can use the following default configuration:
Example of FraudReason: