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
- a024942040c176c812c83ea345d8d4d8fbb142aa2bb2f7c43660772612ebc11c
- request
- 008850c91c182d3483c290303838b058da039cf308794c257a2cdd4b8167cf16
- transaction
- 13d1313bb2d5014b3a887019c06198593000cf8de3c95caccd7ccbb2ba5923b4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20381
the chainentry 20381
- sealed to the entry before
- a558d021ed1c9fdee6b6203829e3a2a5ea6856a7457835ecfc209cb47f65fa58
- this leaf
- 4e317165482ec38a071429492a9aeebd5246b7257436d9cc38ba49b705144268
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RGB9NuatUoD9sCnnX/SZn2BjnuyXAKpr5WTeDvRzuMlmEH/NCGyBVWYuGuvuYkhSE8vyFHPUC9hzcDSdzmRdCg==