HiveRemit · cross-border remittance, attested

Travel-rule-compliant remittance, on USDC, in seconds.

Every cross-border transfer carries a Hive-attested identity receipt on both the sender and the recipient. It meets FATF Travel Rule, US BSA, EU TFR, MAS Notice 626, and FinCEN rules as a side effect of the receipt rail, not as extra work. This is the remittance corridor an MSB, a bank, or a large sender can actually run at scale and stay legal.

Talk to Steve Verify a receipt

Why this exists

Cross-border remittance is a multi-billion-dollar-per-day flow that legacy stablecoins handle informally and that regulated institutions cannot legally touch at scale. The reason is identity: FATF Travel Rule, US BSA §1010.410(f), the EU Transfer of Funds Regulation, and equivalents in Singapore, the UK, the UAE, and India all require originator and beneficiary identity to travel with the funds. Stablecoin rails today do not carry identity in any standard way. HiveRemit binds Hive-attested identity to both ends of every USDC remittance, in a CBOR-canonical receipt that every counterparty can verify offline.

What HiveRemit attests

Every cross-border remittance carries a dual-signed (Ed25519 + ML-DSA-65) post-quantum-ready receipt with travel-rule identity on both ends. The 10 attested states under HiveRemit:

originator_attest: we check the sender's identity, sign the KYC tier, and record the beneficial owner where required.

beneficiary_attest: the receiving institution checks the recipient's identity and signs it at the boundary.

corridor_screen: we screen the corridor against sanctions lists, PEP lists, and high-risk jurisdictions. The CLEAN-MONEY gate has to clear.

purpose_bound: we record the purpose of the transfer and bind it to the receipt. Family support, a B2B invoice, payroll, or charity: each one gets its own type.

fx_locked: the FX quote you actually got is bound to the transfer, with rate, venue, and timestamp.

travel_rule_payload: we build the FATF travel-rule message, sign it, and send it through the receiving institution's preferred protocol (Sumsub TRP, Notabene, TRISA, GTR, OpenVASP).

settlement_init: USDC starts moving on Arc. The receipt opens.

settlement_final: the USDC arrives. The settlement receipt closes, and the beneficiary institution acknowledges it in the same channel.

fiat_off_ramp: the beneficiary converts to local cash. That step is tied back to the original receipt ID.

regulator_export: the full chain of custody can be exported to either regulator on either side of the corridor. It is dual-signed and can be checked offline.

Built for USDC on Arc

The remittance corridor a regulated institution can actually run.

HiveRemit settles in USDC on Arc with sub-second finality and identity-bound receipts on both ends. Every corridor a bank, MSB, or institutional remitter operates becomes legible to its supervisor on demand. Tether-denominated corridors do not have this property and cannot acquire it under their current structure. USDC + Hive does.

Who runs on HiveRemit

Money services businesses moving payroll, family support, and B2B remittances across the US-Mexico, US-Philippines, US-India, US-Nigeria, GCC-South-Asia, and EU-Africa corridors at scale.
Banks that want to add an agentic remittance product line without bolting on a non-supervised stablecoin rail their compliance team will not sign.
Payroll providers moving funds to globally distributed contractors and remote employees under tax-jurisdiction and AML constraints.
Marketplaces and platforms paying creators, sellers, drivers, and gig workers across borders, where the platform itself is the originator of record.
Humanitarian and aid organizations distributing funds in jurisdictions where every transfer is reviewed and the audit trail is the difference between operating and not.

Pricing

$0.0096

Per attested event

Standard tier. ~$0.10 per typical 10-event corridor cycle. Settlement in USDC on Arc.

$0.0192

Per event · Regulated

Regulated tier. Travel-rule message routing, sanctions screening, regulator export portal.

$4,999

Per month · Unlimited

Flat-rate enterprise tier for MSBs, payroll providers, and platforms. White-label available.

Why now

The FATF Travel Rule is now enforced across the G20 and most of Asia. Every jurisdiction has set its own threshold (€1,000 in the EU, $3,000 in the US, S$1,500 in Singapore). Compliance is no longer optional.
USDC is the only stablecoin a regulated institution can use to clear cross-border remittance today. Other rails are either delisted under MiCA, fail compliance checks outright, or are politically off-limits for major banks.
Hive already runs EU AI Act compliance in production. HiveRemit receipts meet EU AI Act audit-trail rules as a side effect, so there's no second system to build and no extra pipeline to run.
The money that flows informally through legacy stablecoin remittance today becomes a formal, bankable market the moment a credible identity layer shows up. HiveRemit is that layer. The volume already exists. The missing piece was the rail.

A direct conversation, not a procurement cycle

If you run a remittance product line, a corridor desk, a payroll platform, or a regulator-facing institution and you want the travel-rule problem solved at the receipt layer, the fastest path is a direct note. Steve reads them.

Talk to Steve See a verification

Live since 2026-05-18 · Dual-signed (Ed25519 + ML-DSA-65) · FATF Travel Rule / US BSA / EU TFR / MAS 626 / EU AI Act aligned · Settles USDC on Arc and Base 8453