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
- ea4bd3689d53e19c7843bba3a7e4fcadb4860339a3d7a345515afad137f67748
- request
- a785c7668e2cc9c2a59914d12702ee1acf48c6019bfb4b0f58a241a7efe4e205
- transaction
- 267a25550435e92cfcad2ac97591c17f62c2b41c495c102815943a1448c2b961computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4116
the chainentry 4116
- sealed to the entry before
- 27fe872569ba8ba42d9d1b661fab16924ee44cc0bb574c8a9cd5eaeacd9b53c4
- this leaf
- a2b50c253329587503f95cbffe77cfd8237df7849ddf95e77d0d5905fb3f1834
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nSdD9nIkiEBbVrX1hRzurFHMGFmnGRpnv04r4DvjEPF8gMjFCikhr5JwvPMAZYtU2GDgiB9VCgKFWFSPBbIYBQ==