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
- 62cf3b31fda8e38877c53191a6ac08d67397eba224a3e02e9336a82b745d7b47
- request
- 6ce7ccb7711c65ca016b1303cfda3fd193bd37163d219ad2b19f0609cb2f5523
- transaction
- 50c49d99860c76263592f7a308a8a1952243771d88e0f750b063d877a06e7e33computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75391
the chainentry 75391
- sealed to the entry before
- 0ec5a912870f00c23e0dc3d763b2b2f6e33adb9f42934582a10bd741498a7059
- this leaf
- ec0988ccaf5300dc95aa253f9f89c2879e314b9a5bcf3fc9c37f0494ecfc01d7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- i31xhQBlBaCXy7/ikfkEKssfu+FZuMGRpHyx6xChqeh2CBlMug7p11tkmHVV8axKybYT49t9ykMLiZON+xL1DA==