1. Wallet and mandate id
2. Mandate terms
The contract requires the account that sends the creation to equal this address.
A Stark curve public key, not a wallet address. The holder of its private key can reserve, and can never change a destination.
3. Permissions
Each entry needs exactly supplierClaimPublicKey, maximumAmount, validAfter, approveBefore, claimBefore and purchaseCommitment, as decimal or hexadecimal strings. Amounts are in the token's smallest unit. Salts are generated locally and never typed.
4. What becomes public?
This preview is computed locally, before anything is created. Read it before you continue.
No permission set previewed.
5. Encrypted backup
The set is never published. Lose this file or its password and the permissions can never be proved again: the money stays reclaimable by you, but no supplier can ever be paid from it.
6. Verify the backup restores the previewed root
This decrypts the file you just downloaded, rebuilds the tree from its contents and recomputes the root. Creation stays blocked until the recomputed root equals the previewed root.
7. Create the mandate
The wallet confirms and prices this call. This page cannot cap a network fee: reject the wallet confirmation if its fee is higher than you accept.
State: READY
Exact call
No call built.
Transaction hash
No transaction hash for this attempt.
Only needed when the outcome is UNKNOWN and no hash was returned. An unknown outcome is never permission to send the call again.
No public receipt read.
Mandate totals
Five separate numbers, in the token's smallest unit. Available is what a reservation may still draw on.
- Fundedunread
- Availableunread
- Reservedunread
- Paidunread
- Reclaimedunread