why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- 0c574d8ae801af68c032330970863f5177ae1a16316bd2326149426e95f91c8e
- request
- 9bb981b05dd7a4407b0bc1deb523b2f58bddf9b927ff56288bbaa08f1915221b
- transaction
- 0a5e51ed959504da157cc0cf4d4cfccae9d968b2246a8e4b3f5233d3d141522ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44322
the chainentry 44322
- sealed to the entry before
- 3574161ddadf6e0006a7173902f161f7e68230fb7925b91e74e6d89d5fe30d4a
- this leaf
- 9fcc1805b23bc9ecf37c0d2a9b3980921614577570066387fcc67f5c46899589
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UwtLIjM1XUxxmeZ2EskODxhVa1Htv/kkny9pqDMyHPG7gsuqYCskAobpp5cijdnVvGJNOOZY523PFcGZvSGcBw==