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
- 7b54dc04ad816ceedca2f1415bf6442fab462d3637f768d8966823f47472ccfc
- request
- 1b9a66ac2d377d7d4dd2c00682b3c775b8f0a2ddce9cc0a818ad408467960567
- transaction
- a8c4f188f056bde79153d17763f2f4d0563958c61dfdd2c1b005e8367d6a55d5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41380
the chainentry 41380
- sealed to the entry before
- 493ae1e09dcf965b0b3da4a434c913d5b4ad4e2aa00fbdba453e73b48459ddc1
- this leaf
- 8d770a9443b71a2f6c35d7d2b634e44fdc318a7557725064be955d1004bfa1cf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nWOETKbIgM2+re/3st0QcE/EuY1i3LUD/eGSVbjC2mxRipuAHGGyiiZ0pRh+/zDiexKOTkdk6S44TLPLRjxyAw==