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
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.
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.
One pipeline from a raw address to a decision you can defend to a regulator.
Add a wallet or call the SDK. Hera follows it on-chain: payments, path payments, token transfers and the internal calls generic tools miss.
Every subject gets a 0–100 score with the reasons behind it: sanctions, counterparty exposure, behaviour. No black box.
Allow, review or block. Alerts land in a queue, webhooks fire, and the Travel Rule message is ready to send.
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.
Decoded. Account GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN, muxed ID 42.
Decoded at the edge with checksum validation, then carried through screening, alerts, Travel Rule and records. The sub-identity is never flattened away.
Memo IDs route funds to an end user at a shared address. Hera scores that user's own transfers, not the whole omnibus account.
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.
ETH paid out by contracts, like mixer withdrawals, only shows up in traces. Hera reads them.
ERC-20, ERC-721 and ERC-1155 transfers, normalized next to native value.
EIP-55 checksums are verified, so a mistyped address is caught before it's screened.
Base, Arbitrum, Optimism and Polygon on the same engine.
Collect IVMS101 originator and beneficiary data, check it against the right jurisdiction's threshold, find the counterparty VASP, and track the message to settlement.
Pick a jurisdiction and an amount. This runs the same check the API does.
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.
| Jurisdiction | Data required from |
|---|---|
| USD 1,000 | |
| USD 3,000 | |
| Every transfer | |
| EUR 1,000 | |
| SGD 1,500 | |
| CAD 1,000 |
One call before you sign or credit a transfer. Pass an M… address or a memo and Hera handles the rest.
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);
}For builders and startups.
Self-serve
For larger organizations that need compliance at scale.
Custom
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.
Stellar and Ethereum today. Base, Arbitrum, Optimism and Polygon are next.
Hera decodes M… addresses and memos into the underlying customer and scores that customer's own transfers, separately from the shared account.
IVMS101 payloads with Hera-to-Hera exchange first, then TRP interoperability. On Stellar, counterparties are discovered through their stellar.toml.
Hera put the eyes of Argus on the peacock's tail. We put them on your transfers.