How the Exchange works
The FIL Exchange lets its members share and use data about fraud events.
Members and users
Telecommunications companies and vendors register as members. In the API a member company is called a peer and is identified by its peerId. The people who work for a member register as users of their company.
Users submit information about suspected or confirmed fraud: an identifier such as a phone number or an IP address, the type of fraud, and the countries involved. In return the company earns tokens, which it spends on the fraud events submitted by other members.
For the roles of users and how registrations are approved, see Roles and approval.
Data on the Exchange
The Exchange holds fraud events as contributions.
- Members upload contributions. Uploads keep the data of the Exchange current and earn tokens.
- Members download contributions to update their own records and to block the fraud other members have seen.
- A member that finds a contribution to be wrong flags it as a false positive.
For the rules of rewards and charges, see Tokens, rewards and limits.
Every contribution and every token movement is recorded in a tamper-evident ledger. See Security and data.
Two ways to work
- The web app is for people. No code is needed.
- The API is for automated integrations: a member's own system uploads and downloads fraud events on a schedule.
Both use the same account. See Getting started.
Keys and signatures
A user signs in by proving possession of a key, not by sending a password.
- The authorization key pair is an Ed25519 key pair derived from the user's email address and password. Its private key signs the sign-in request. See Signing user email addresses.
- The signing key pair is a second Ed25519 key pair of the user, also derived from the email address and password. It signs upload and flag transactions sent through the API. See Signing transactions.
The web app derives the keys in the browser and signs for you. Both key pairs are shown on the Profile page, as Authorization key and Signing key, for use in an API integration.
Because the keys are derived from the password, changing or resetting the password gives the user different keys. An integration that signs with the earlier keys must be updated.
Second sign-in step
A user can protect sign-in with a second step: a one-time code sent by email, an authenticator app, or a passkey. It is set up on the Security tab of the Profile page.
The following rules apply to the emailed code:
- The code is sent to the user's registered email address.
- A code can be requested once per minute.
- A code is valid for 5 minutes from the time of the request.
- Only the most recently sent code is valid.
- A code works once.
For signing in through the API with the emailed code or an authenticator app, see Authorizing an account. A passkey cannot be used by an API client.