Peloryn Verify · Tier 2 Early access

Prove you checked.

When a list-screen isn’t enough, Verify produces an Enhanced Due Diligence report — source-backed identity, sanctions, ownership and behavioural context where available, plus a timestamped, hashed file built to support banking or investigative review.

Early access · founder-led sample reports · built around EU 16th-package “facilitate” due-diligence pressure

PPeloryn VerifyEnhanced Due Diligence
ReportEDD-2026-041828 Jun 2026 · 09:41 UTC
MT Arendal Spirit · IMO 9514306  ·  Counterparty: Vantor Shipping Ltd
ReviewOwnership resolution boundary at layer 3 · one behavioural flag
11-section report
§1 Vessel identity
§2 Sanctions screening
§3 Ownership & control
§4 Counterparty risk
§5 Behavioural risk
§6 Dark activity
§7 STS history
§8 Port-call pattern
§9 Evidence trail
§10 Limitations
§11 Decision support
SHA-256 · 9f2c8e51b3d0…4a71b6 Evidence Vault
List versions · OFAC 28 Jun · EU 16th pkg · OFSI 27 Jun · UN 26 Jun
Why now

The standard shifted from list-screening to behavioural evidence.

The “facilitate” offence

The EU’s 16th package (February 2026) made it a criminal act to facilitate an unsafe or uninsured tanker — pulling bunker suppliers, traders, and port agents directly into the sanctions chain.

“On notice” by behaviour

OFAC now treats AIS due diligence as indispensable as list-screening. You are on notice based on available behavioural data — not only on what has been published.

Rotterdam enforces first

The FIOD arrested four people in Rotterdam (July 2025) for supporting shadow-fleet vessels — suppliers and service providers, not shipowners. A screenshot is not a defence.

What Verify proves

Depth where resolved, behaviour where fresh, and a file that survives review.

01 · Depth

Who is behind it

Ownership and control are mapped when approved source data is present, with 50% rule logic and an honest resolution-boundary statement where the trail ends.

02 · Behaviour

What the available context shows

Mercury and Atlas behavioural context can surface AIS gaps, STS history, dark activity and port-call patterns when fresh rows are available — each point named and explainable.

03 · Defensibility

A file you can hand the bank

Every report is timestamped (UTC, server-side), list-version-stamped, and SHA-256 hashed. If a single character changes after generation, the hash changes — proving the document was altered.

Inside the report

One workflow. Eleven sections. One defensible file.

Enter an IMO and a counterparty name; Verify returns an Enhanced Due Diligence report with every populated section, every source version, and every unresolved gap made explicit.

§1
Vessel identity

IMO, flag, P&I club, prior names and flags, MMSI↔IMO mismatch flags.

§2
Sanctions screening

Vessel and associated entities vs OFAC, EU + annexes, OFSI, UN — with no-hit records and list versions.

§3
Ownership & control

Imported ownership layers with 50%-rule logic and an explicit resolution-boundary statement.

§4
Counterparty risk

Company age, jurisdiction, and sanctions exposure of the entity you are dealing with.

§5
AIS / behavioural context

An explainable review rating when fresh Mercury or Atlas rows are available — every contributing point named, not a hidden score.

§6
Dark activity

AIS gaps assessed with proximity scoring — where the silence happened, and whether it matters.

§7
STS history

Ship-to-ship transfers with ARA-barge false-positive suppression, so routine bunkering isn’t flagged as evasion.

§8
Port-call pattern

Trading pattern with sanctioned-port and high-risk-zone flags.

§9
Evidence trail

Every source, version, and timestamp behind the report.

§10
Limitations

Coverage scope stated plainly — what was and wasn’t resolved. Not legal advice.

§11
Decision support

Clear · Review · Elevated — decision support, never an automatic go / no-go.

§0
Chain of custody

Data-source versions and the SHA-256 hash that seals the file.

The Evidence Vault

Not a screenshot. A sealed record.

Every report is saved to your Evidence Vault — hashed, timestamped, and retained for five years. Re-run a saved record and Verify flags exactly what changed, so a deferred-payment or post-fixture review has a living trail, not a stale PDF.

Supports due diligence — it does not provide legal clearance.

Report IDEDD-2026-0418
Generated2026-06-28 · 09:41:07 UTC
Retention5 years
StatusSealed · unaltered
SHA-256
9f2c8e51b3d0a2f4…6c1e904a71b6

A cryptographic fingerprint. If one character of the report changes after generation, this hash changes — proving the document has been altered.

How it works

IMO plus counterparty in. Defensible report out.

01

Enter the deal

One screen: vessel IMO and counterparty name. No wizard, no staging — under fifteen seconds to initiate.

02

Verify assembles the report

Approved sources populate identity, sanctions, ownership and behavioural context where available, and unresolved sections are shown as honest gaps.

03

Save to the Evidence Vault

Export a timestamped, hashed PDF and drop it in the deal file — the proof your bank has been asking for.

Protect and Verify

Land on Protect. Step up to Verify.

They share one data spine. Most teams screen on Protect every day and reach for Verify the moment a deal, a bank, or an investigator needs proof.

Tier 1 · Screening

Peloryn Protect

“Is it on a list?” A Vessel Risk File in seconds, from €299/mo.

Explore Protect
Tier 2

Peloryn Verify

“Can I prove I assessed it?” A full EDD report, from €1,499/mo.

See Verify pricing
Could your last ten stems pass a FIOD review?

See the report before you need it.

Request a founder-led sample Enhanced Due Diligence report against a real ARA vessel and counterparty. See the evidence file, including what was resolved and what remained a documented gap.