Antifraud Namespace

The telecommunication industry is faced with a variety of fraud challenges. For example toll fraud with “short-stopping” or also known as “short-transit” or “number hijacking.”

In this scheme, call traffic does not reach the terminating country and the fraudster is working directly with a dishonest carrier that sits along the call transit path. The dishonest carrier that receives the traffic short stops it before it continues to the destination country, and then shares revenue directly with the fraudster. These dishonest carriers advertise and terminate numbers without authority or knowledge of the actual number range owner.

Currently, calls are passed from one carrier to the next without transparency, and CDRs only indicate the immediate upstream and downstream carrier.

What is required is a transparent privacy across the carrier chain (A-B-C-D-E model). For example B does not want A and C to see each other to protect his commercial interest.

This could be stopped with a transparent privacy across the carrier chain (A-B-C-D-E model). For example carrier B does not want carrier A and carrier C to see each other to protect his commercial interest. At the same time is very important that A knows if a call has been terminated at E without knowing B-C-D or their commercial interest to be able to avoidance any form of short-stopping.

Please note that the logic can be reversed whereby the origin carrier publishes his call so that the terminating side can validate if a CLI has been modified or spoofed.

Here the Antifraud Namespace can help carrier A if E publishes FuzzyHashes of terminated calls.

The Antifraud Namespace has two main functions:


The RecordCall should be called at the termination end and the function has 4 parameters:

ANumber: This is the caller number.

BNumber: This is the termination number.

StartDateTimeUTC: The start date/time of the call in d/M/yyyy HH:mm:ss format (UTC). The current date/time can be always retrieved in the right format with the helper function: DateTimeUTCNOW

AgreementCode: For extra privacy carrier can agree on extra values for this field. Could be also a salt or any other details of the CDR.

As REST call for example:


CheckCall has exactly the same parameter as the function RecordCall. It returns the values true or false indicating if that call ever has been terminated or not.

As REST call for example:

In case you are behind a firewall or not able to install your own node you might want to have a look at the Blockchain DNS Interface.

Note: We are fully aware that the clocks of the different systems are never ever 100% in sync. For this reason we developed a “FuzzyHash” to allow a bandwith of time tolerance.

Above we explain the syntax of our web services APIs. Kindly note that we offer broad range of APIs such as websockets, RESTful APIs and of course traditional DNS AntiSPAM interfaces. Just contact us and explain how you would like to connect!