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
- 2dc1938c19202a319f5b5bcecbcd51357bdd8ec001ec36018cc3a33ea60b61f1
- request
- 3a8fb5aec0379ae2bfef76d4a23c5de594bf7d2697f69dc1dc08389d5aee8ff3
- transaction
- 3b77f6fcac51df67e69cf3765694b07ddbf11162e64a5341a6f726fb0cf9ec26computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30913
the chainentry 30913
- sealed to the entry before
- 6680533a2555a84b28a8469bf04e55f5e1a184553a0c8d1e257a3c17eeddee7b
- this leaf
- f9439c19e73a28c4f6bc6513e57ad24c27d7d1b5f6e04a42e4c9060aa0fdcaec
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5yXeOnixY7M+F5O9+AQENsJYWs445l8oXQqI9nQeLieFBtYZJJJaP6O6RzvJ64HOCFoLIgB5s7kJtc9u+1n6Bg==