Dollars and euros, on one rail.
Trade runs in dollars; Europe runs on euros. eUSD is planned first and eEUR after it, on the same confidential design, so a business can hold and move both.
Why a euro token too.
MiCA caps how widely a non-euro token can be used for payments inside the euro area. Push the daily use up and see when the cap bites.
Issue as usual.
MiCA Article 58(3) with Article 23. Averages over a quarter, within one currency area.
Two currencies, one design.
Both tokens are planned on the same architecture. Moving between them is planned as a Forex service, run by a licensed partner: as an issuer, Softseco does not exchange one crypto-asset for another.
- Currency
- US dollar, one to one
- For
- Trade, treasury and cross-border payments
- Amounts
- Encrypted, readable on lawful request
- Rules
- Vigilantis on every transfer
- Currency
- Euro, one to one
- For
- Everyday payments in the euro area, with no cap of this kind
- Amounts
- Encrypted, readable on lawful request
- Rules
- Vigilantis on every transfer
Who needs both.
Importers and exporters
Pay suppliers in dollars, get paid by customers in euros, and keep both sides of the margin private.
Teams across borders
Pay people in the currency they live in, from one treasury.
Treasuries holding both
Rebalance between dollars and euros in seconds, without publishing your exposure.
Working across currencies?
Tell us which pairs and flows matter to you. It shapes what we build after eUSD.