Skip to content

Home/Sectors/Banking & finance

AIS data for trade finance that stands up to internal audit.

Screen a vessel before drawdown, reconcile trade documentation against the vessel’s actual movements, and monitor the exposure until the facility is repaid. AIS data for trade finance from our own network, delivered in real time, with the raw signal and its provenance intact.

100,000+

Vessels tracked / day

49M+

AIS positions / day

40+

Countries covered

<5s

Antenna to your API

A vessel screening decision is only as defensible as the record beneath it.

When internal audit asks how a vessel’s position was established, a conclusion that cannot be reconstructed is not an answer.

  • Risk scores arrive stripped of their evidence.Most AIS reaches a bank already cleaned, fused and reduced to a risk score. Adequate on a screen, inadequate in a credit file, because the output cannot establish what the raw signal was, which independent receiver collected it, or at what moment.

  • Disablement and coverage loss present identically.A disabled transponder and a gap in a single provider’s coverage are indistinguishable, so dark activity flags carry false positives into credit decisions. The OFAC, State and Coast Guard advisory of 14 May 2020 asks institutions to monitor AIS manipulation, not only AIS disablement.

  • We supply observations, not assessments.We operate our own infrastructure, terrestrial and ship-borne, with satellite feeds for open ocean. Every position is nanosecond time-stamped and trust scored by our anomaly detection models. We are neither a screening platform nor a reseller: your models, your risk appetite, our observations underneath.

Bring us a vessel on your book.Send an IMO number or MMSI, and we will return what our network collects on that vessel, with receiver metadata and trust scores attached.

Verify an IMO against our data

From pre-drawdown screening to monitoring the exposure until repayment.

  • Pre-transaction screening on a vessel, cargo or counterparty

    Before drawdown, examine how the named vessel has actually behaved: AIS gaps, ship-to-ship transfers, port calls, MMSI reuse, IMO mismatches and flag hopping. Enhanced due diligence on an SDN or OFSI match concludes faster when the underlying messages remain available rather than summarised away.

  • Reconciling trade documentation against the vessel’s movements

    A clean on-board bill of lading naming a load port the vessel never called at is among the oldest frauds in the market, and falsified shipping documentation is named as a primary evasion practice in the 2020 OFAC maritime guidance. Under UCP 600 the desk examines documents, not events. Port call verification against independently collected positions allows the shipment to be tested before drawdown, and phantom cargo pledged to more than one lender to be identified.

  • Monitoring the exposure across the credit lifecycle

    Origination screening decays quickly. Shadow fleet designations refresh constantly, vessels change name, flag and MMSI mid-voyage, and a transhipment can surface weeks after the facility is drawn. Continuous voyage data allows the exposure to be monitored through to repayment rather than assessed at a single point.

  • An evidence pack for audit, a regulator or a SAR filing

    A dashboard screenshot is an image. What makes a file defensible in an OFAC or OFSI enquiry is the ability to evidence where the underlying data originated: which receiver collected which message, when, and how strongly it was corroborated. Provenance travels on every position, so the file rests on observations rather than on an opinion that cannot be reproduced.

  • Ship finance collateral and Poseidon Principles reporting

    Collateral that moves requires voyage-level data at portfolio scale. Track utilisation, laden and ballast legs, and trading patterns against covenant restrictions. Poseidon Principles climate alignment is calculated from verified IMO DCS fuel data rather than from AIS, but voyage records allow a borrower’s reported activity to be corroborated against observed movements.

  • Raw positions for research and trading desks

    Nowcast seaborne flows, floating storage and export volumes ahead of official statistics, on the same observations the live feed carries rather than on a finished figure. Take raw NMEA over TCP, a REST API or a WebSocket stream, and run proprietary models on data that can be inspected line by line.

How the data is produced,
and how you can check it.

Every station runs the same dedicated, standardised hardware, encrypting each message at the moment of capture.

Monitor

Cover the vessels you finance

Track 100,000+ vessels a day across 40+ countries, so an exposure can be watched across the life of the credit instead of screened once at origination.

Verify

Know which receiver collected it

Every position is nanosecond time-stamped and given a trust score by our anomaly detection models, so manipulated or spoofed signals are flagged rather than quietly merged into a clean track.

Act

Into screening, credit and the audit file

Take it as raw NMEA over TCP, a REST API or a WebSocket stream, in under five seconds from antenna to your API, on licence terms written so the data can go into your own systems and not just a vendor portal.

AIS data for trade finance: the questions credit and compliance teams ask.

How do banks use AIS data for sanctions screening?

Screening generally operates in two layers. Vessel identifiers are matched against SDN, OFSI and EU designations, and behaviour is then reviewed for indicators such as AIS gaps, ship-to-ship transfers and calls at restricted ports. The first layer is a list problem and decays between updates. The second is a data problem, and it is the one we address: we supply the position layer beneath the screening engine, with the receiver metadata that makes each observation independently checkable.

Can AIS data be used as evidence in a trade finance dispute?

Admissibility is determined by the tribunal, not by a data provider, and in practice it turns on provenance: whether the origin of the data can be evidenced and its integrity demonstrated end to end. Our messages are encrypted on the hardware at the moment of capture, nanosecond time-stamped and carry receiver metadata, so the chain from antenna to file is documented rather than asserted. We can supply the underlying records, not only a chart image.

What is the difference between an AIS gap and AIS spoofing?

A gap is absent data. Spoofing is present data that is false. The two call for opposite conclusions in a credit file and are routinely conflated, because on a single feed a disabled transponder and a hole in that provider’s coverage are indistinguishable. Trust scores and receiver metadata establish whether coverage existed during the window, and comparing what independent receivers collected for the same area separates vessel-originated manipulation from area-wide interference affecting every ship present.

Do you cover the vessels and the routes on our book?

It depends on the vessel and the area, because we supply only what our own network collected. Send the IMO number or MMSI and we will state plainly where our reception is strong and where it is thin, on the raw result rather than a coverage map. Every position carries the receiver that collected it and a nanosecond time stamp, so the credit file rests on observations that an auditor can check rather than on a figure taken on trust.

Is AIS data reliable enough to base a credit decision on?

AIS is self-reported, so a position is a claim before it is a fact, and any feed presenting it otherwise overstates what it knows. Reliability derives from provenance: which independent receiver collected a message, at what moment, and how strongly the surrounding observations corroborate it. That is what a trust score records, and it is why we release the underlying data rather than a figure that must be taken on trust.

Start with the vessel you cannot get comfortable with.

Send an IMO number or MMSI, and we will return what our network collects on that vessel and the origin of every message.

Verify an IMO against our data