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
- cf3bbf629fcd262d576f4bbcdd6035c956592d8c22fd2a94ca0cd7b0055db7ee
- request
- 67d5da71e78405ac1ddc287062203109b670855c4240ca0aa2a2b6eeedfa3496
- transaction
- 6425cde5d14ed27b9e2d92ab4896d8c777ff27808648c340ecf18c6c609f880ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58888
the chainentry 58888
- sealed to the entry before
- b387d4940b7c48eea5ef1d296f7df8af15836620d41c256367857da053c398fe
- this leaf
- 75ffd71550d68a4d13a04bc2d81501b80ee4b46891efa430aa43835698cdf599
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MBOnmUth6gkVT078PSPBFgvQzk6aHrRHnr7+zO7xVjR8odt7Xp4/SIdedAv911itNwQuk021CiH06R3Ql6BmDQ==