Reporting

Contribute to the FNC-RF database. This section lets you create and manage fraud reports on an IBAN, and qualify accounts you are responsible for.

Reports and alerts

• A report is one institution's contribution about an IBAN (the fraud you observed).
• An alert aggregates all reports for the same IBAN across the ecosystem. Creating a report attaches it to the matching alert (or creates one). You consult alerts from the Alerts section.

You can act in two roles:

• Reporter — you saw a fraudulent transaction and report the suspicious IBAN.
• Account holder — you manage the suspicious account, so you can qualify it (confirm fraud, mark genuine, …) or flag it as a participant in a related attempt.

Endpoints

Creating a report

Provide at minimum the iban, the bic of the PSP managing the account, the date of the event, a fraudCategory, and a transactionType. You may also add a fraud source, transaction channel, the victim's BIC, and a free-text comment.

The response returns the resulting alertId and reportId (usable on the Qombo web platform), plus any pre-existing alert for that IBAN.

🚧

One pending report per IBAN

If your institution already has a pending report on the same IBAN, creation is rejected with status: "blocked" and details of the existing alert instead of creating a duplicate.

Qualifying and updating

• Holder qualification records how the account holder assesses the account (confirmed fraud, identity theft, genuine, merchant, …). This is what drives an alert toward CONFIRMED or REJECTED.
• Participant qualification records that the account was involved in a related attempt (SIGHTING) or clears a prior suspicion (FALSE_POSITIVE).
• Update context lets you enrich an existing report with the fraud source and/or transaction channel after the fact.

📘

Codes and full schema

The exact values for fraudCategory, transactionType, fraudSource, transactionChannel, and the qualification codes are listed per endpoint in the API reference.