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
- 595e35cc48a09e61a892f1565eb4472c558dc55db424d12e6003b9a1c0a7fdb1
- request
- 3a1f978dafaad50f9db7f08fae0aab2bf65200639009461239a3c32273173cde
- transaction
- 260901138ef07199529d94f555183e142f15c29d73e54b829ff54e11c4398e1fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66218
the chainentry 66218
- sealed to the entry before
- 15b17890a5b1fe6921e243570d5044ec2e54baf020a11f9e312611c5af5e0c37
- this leaf
- e3321ba0a6710e41d2cc470dba1bc994116a5a783c53797cbe43ed283dd35d07
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RBEzgFLrgw9G/bFkywJsM84CCpE363XFV4iED/GaEAEwrk1slwY6R38Ab1/qH2bMWOZguZYNX5Zu4moVFRwyDA==