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
- 88e141bf1e4eb1b412f6310a3a65f6d083c4ad564970aa5ce3070b4789655ffe
- request
- 6908e01a790bf62c39a1443358f49cad84f3d7413f55f9fe23bf1fa8d1c4aec9
- transaction
- f953d7d8b68ccab94de5b17d8f6359ba89988dd788b79bb7a3ee8e8af4f2d2efcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64727
the chainentry 64727
- sealed to the entry before
- 23cfb4caad2891295bf1914c1683d587e21d978d568c2fa9dcecb8c29aa35db7
- this leaf
- 3c7410e36bc07098d352411a53cd777f774556244bb60524ae24bcfc426f5093
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1ImvpuxcvqzoD4T9w8BwyhfsllK+y5wuRy+KiWxS2el0v1QL1VP9mBTmx5AoiMpJL1hAptg3+ATSxoAHaEKiBg==