- When the cashier converts some rupee to FLO ( when user min-FLO balance is low), Appends (to note) the actual token (rupee) amount sent
- ie, note for those requests will be <txid>#<rupee_amt>
-- changes user flow for wallet top-up and changed the visual design to reflect that
-- top-up now works with random generated string
-- removed UPI ID asking step
-- implemented required changes to cashier side also
-- implemented rule to include UPI ID while topping up
-- cashier can now see which UPI ID sent the money
-- Scanning QR code is collapsed by default to save space
-- decline request now shows a loader
- Send FLO to user if their balance is below user_flo_threshold
- Automatically converts rupee token equivalent of send_user_flo value using exchangeAPI
- user_flo_threshold and send_user_flo are blockchain configured
- Encrypt UPI ID of users before sending to cashier
- Cashier: reconnect status ws at a regular interval to avoid timeout
- return the default cashier ID if no cashier is online (configured via blockchain)
sendTx:
- check total balance before processing utxos
- reject "Insufficient FLO: Some UTXOs are unconfirmed" when balance is there but some utxo are used/unconfimed
- Removed default values from floGlobals
- Default values are now in their respective modules
- The following properties of floGlobals can be use to override the default values of respective modules: apiURL, sendAmt, fee, tokenURL, currency, SNStorageID
- Default/current values can be obtained from each module with getter properties
- Some current values can be set with setter properties
- The containers for appObjects, generalData, lastVC are now in floCloudAPI module. Also automatically adds get/set properties for them in floGlobals. Thus can be accessed from floGlobals as before