Live on Stellar + Ethereum · Travel Rule ready

Compliance that never blinks.

Hera screens wallets, scores every transaction and handles the Travel Rule across Stellar and EVM chains. Our own intelligence, no resold vendor data, and native support for muxed accounts, memos and SEPs.

  • SEP-23 native
  • IVMS101 Travel Rule
  • Every score explained

Example 1 of 3: A muxed Stellar address for a customer of Circle's USDC issuer account. No sanctions match, no risky counterparties. Score 7 of 100, low risk, clear.

IllustrativeEvery Hera score is explained line by line.
  • Stellar
  • Ethereum
  • USDC
  • EURC
  • XLM
  • ETH
  • USDT
  • Base, coming soon
  • Arbitrum, coming soon
  • Polygon, coming soon
How it works

Watch. Score. Act.

One pipeline from a raw address to a decision you can defend to a regulator.

01

Watch

Add a wallet or call the SDK. Hera follows it on-chain: payments, path payments, token transfers and the internal calls generic tools miss.

  • 2,500 USDC12s ago
  • 0.42 ETH1m ago
02

Score

Every subject gets a 0–100 score with the reasons behind it: sanctions, counterparty exposure, behaviour. No black box.

  • +100 SANCTIONS_DIRECT
  • +15 RAPID_IN_OUT
  • +20 STRUCTURING
03

Act

Allow, review or block. Alerts land in a queue, webhooks fire, and the Travel Rule message is ready to send.

  • Allow
  • Review
  • Block
Built native on Stellar

EVM tools see one address. Hera sees the customer.

Exchanges and anchors put thousands of customers behind one Stellar account. Screening the shared address tells you nothing. Hera decodes who is actually on the other side, and keeps that identity through every check and record.

ACCOUNT · holds the balanceGA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN
MUXED ID · the actual customer42

Decoded. Account GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN, muxed ID 42.

Muxed accounts (SEP-23)

Decoded at the edge with checksum validation, then carried through screening, alerts, Travel Rule and records. The sub-identity is never flattened away.

Memos

Memo IDs route funds to an end user at a shared address. Hera scores that user's own transfers, not the whole omnibus account.

SEPs and anchors

Anchors are identified through their stellar.toml (SEP-1), and only when the toml lists the account back. SEP-10, 12 and 31 endpoints feed the Travel Rule.

And EVM, traced properly

Not just tx.value.

Internal transfers

ETH paid out by contracts, like mixer withdrawals, only shows up in traces. Hera reads them.

Every token standard

ERC-20, ERC-721 and ERC-1155 transfers, normalized next to native value.

Typo guard

EIP-55 checksums are verified, so a mistyped address is caught before it's screened.

More chainsSOON

Base, Arbitrum, Optimism and Polygon on the same engine.

Travel Rule

Travel Rule, without the spreadsheet.

Collect IVMS101 originator and beneficiary data, check it against the right jurisdiction's threshold, find the counterparty VASP, and track the message to settlement.

Does the Travel Rule apply?

Pick a jurisdiction and an amount. This runs the same check the API does.

Counterparty wallet
Travel Rule applies

FATF baseline requires originator and beneficiary data for USD 1,000 and above.

Threshold ≈ $1,000FATF Recommendation 16

Amounts in other currencies are converted at a rough fixed rate here. Thresholds must be confirmed with counsel for your program.

Default thresholds · configurable per org
JurisdictionData required from
USD 1,000
USD 3,000
Every transfer
EUR 1,000
SGD 1,500
CAD 1,000
For developers

Your first screen in five minutes.

One call before you sign or credit a transfer. Pass an M… address or a memo and Hera handles the rest.

  • REST API and a TypeScript SDK
  • Signed webhooks for wallet activity and alerts
  • Scoped API keys you can revoke any time
screen.ts
import { Hera } from "@hera/sdk";

// Server-side only: the SDK refuses to run in a browser.
const hera = new Hera({ apiKey: process.env.HERA_API_KEY! });

const result = await hera.screen({
  address: "MA5ZSEJY…AFJOYK", // muxed: decoded for you
});

if (result.decision === "block") {
  throw new Error(result.reasons[0]?.title);
}
Pricing

Two plans. No surprises.

Developer

For builders and startups.

Self-serve

  • SDK and REST API
  • Wallet monitoring
  • Real-time transaction tracking
  • Sanctions screening
  • Risk scores with reasons
Start building
FULL KYT + AML

Enterprise

For larger organizations that need compliance at scale.

Custom

  • Everything in Developer
  • Full KYT and AML
  • Advanced risk scoring
  • Travel Rule (IVMS101)
  • Alerts and case management
  • SSO, roles and audit export
  • Dedicated integration support
Talk to us

Compare the plans in detail

Questions, answered

Do you resell Chainalysis or other vendor data?

No. Hera's labels come from public records (OFAC, UN, EU and UK lists), on-chain facts, Stellar SEP-1 attestations and our own analysis. Every label shows where it came from.

Which chains do you support?

Stellar and Ethereum today. Base, Arbitrum, Optimism and Polygon are next.

How do muxed accounts and memos change screening?

Hera decodes M… addresses and memos into the underlying customer and scores that customer's own transfers, separately from the shared account.

Which Travel Rule protocols do you support?

IVMS101 payloads with Hera-to-Hera exchange first, then TRP interoperability. On Stellar, counterparties are discovered through their stellar.toml.

Put a hundred eyes on every transaction.

Hera put the eyes of Argus on the peacock's tail. We put them on your transfers.