01
Verified accounts
Investor and issuer prove control of their Ethereum L2 and Radix wallets by cryptographic proof.
Security registration
The security is registered only after payment verification
The proposed process links a payment made independently between investor and issuer to security registration. Payment verification is still planned. References to Ethereum L2 describe the illustrative technical scenario; payment services and integrations still need validation.
Payment and registration are separate steps. The model provides for registration only after successful payment reconciliation. Payment and security delivery are not a single indivisible operation (atomic DvP).
02
Subscription
The investor specifies the amount to subscribe. The platform creates a unique payment reference for the transaction.
03
Direct payment
The investor pays the issuer's Ethereum L2 wallet using the assigned payment reference.
04
Verification and entry
Only after consistency checks does the platform record ownership on the investor's Radix wallet.
The payment reference
A unique identifier connecting the payment instruction to its subscription and registry evidence. It associates:
- investor and issuer;
- the parties' Ethereum L2 wallets;
- the parties' Radix wallets;
- the minibond identifier;
- principal amount and price;
- total issuance and subscribed amount;
- duration, coupon frequency and rate;
- the token selected for payment.
Checks before registration
The model requires consistency between the payment reference, the observed payment and subscription data, together with valid wallet-control evidence and the applicable eligibility checks.
PaymentCash-leg event
ReconciliationReference and amount
ValidationWallets and rules
DLT registrySecurity assignment