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
- 2597565e6b590569cd2a4ff151ac5441dfe649972cbd2ae6c6d19bc3a2ce0935
- request
- eba7c831249bab9cb60bf9ff7cd6b8472499f25a4300cf2f0ec145cf847f588a
- transaction
- 982d97aa63826def699becc94d07d28bba9639ec8e6db56b5eb816c28addc80bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3770
the chainentry 3770
- sealed to the entry before
- 253acbd2642ac1c8dbdca89abc3abc80030ffab5648a44ae632a975935994f14
- this leaf
- b6dc54d70ea08ea4b2240a317c4f54979b83b318e4d1c79f718d855399da37c0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +cRH4dD5ZKRQ4bi1TaL2Jipyaj9qcYUEWYKzyGAnRYXlQOC4Guf2+EbqzMIpKelcK0TKBgy2LsRL6BdDmC+XDg==