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
- ea9c151f998e37b745b7dcad671b3f842af06baa016c4d832127a86f6ef5e118
- request
- 6bbe2f77844c64565af80ee84caa8703006a7a09836d6ce0b91a4ef0c9c2d0d2
- transaction
- c0f5e906352f25adaa008a931f83805eddd6624c57294d6cb2d0524c34cf851ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35157
the chainentry 35157
- sealed to the entry before
- 3c2a6f0bd88f585d307bf755dbf4063605aabc56aa4bf672244f3777a0e3f6cb
- this leaf
- feec07d70219c082910b0707534fb2d845e2aea66def14e0e9be1870cbcd4b0a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- z4AFQz8iSMC915vSkjxDybOidS55YSRHHJknnQStG8O6Wh4OwUesATcO+LtLzHgpbkIN5lc+pHSII5In2wCEDA==