You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment all payment transactions are final and the funds are directly transfer from buyer to merchant. We need a mechanism to revert malicious transactions. What we already mitigate is
Caching of transactions. When a transaction is created it expires after x (currently 10) blocks are elapsed, so it must be sent immediately on creation.
Multiple transactions. The contract only accepts payment requests at least x (currently 5) blocks apart, so in a single tap you can only create 1 valid transaction.
Maximum tx amount. This sets the limit on how much can be transferred in one payment.
What we want to mitigate is the merchant showing a different amount on the POS screen from what is actually being requested and also unauthorized taps. An escrow and a reputation system could help identify and punish malicious actors.
The text was updated successfully, but these errors were encountered:
At the moment all payment transactions are final and the funds are directly transfer from buyer to merchant. We need a mechanism to revert malicious transactions. What we already mitigate is
What we want to mitigate is the merchant showing a different amount on the POS screen from what is actually being requested and also unauthorized taps. An escrow and a reputation system could help identify and punish malicious actors.
The text was updated successfully, but these errors were encountered: