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
- dd125753f1ba79190a918f336854eb304090f79d820cc2e40b1106fc81417edf
- request
- f73bec681e4488a678f28cc4d734a02ecb9d7c25e12a2a3bbea654f8deed76a5
- transaction
- 00408b3d8e085e5ab8ba9d7852583e588aafef760f451964c106d99ea11552accomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38139
the chainentry 38139
- sealed to the entry before
- 2d4caa8b030a744700232b287bdb02632bb9ed3de2bfefc179da59670e2db39c
- this leaf
- 616df1095cab895bc6f4d0ddf9928b8645fea74c240dbf489d3ddae800c8ea4a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RUQWlQvRLEVUNo3yH/uJjVM46hmNnkaqdzz1Ed0AV0mjG5B1RdRjiUCtIQfsmtOKtnWMZ4LG8vxdZpM3cavkBw==