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
- 823977afbab4ea621ac2277ed0b9cf7508dea38fecc7f71498071fbb45dcb8c9
- request
- e251175fe593299a667fe21bc46ed15f10b9664952e3b3c338a2140a6deb5b63
- transaction
- b25d0aaa848aaa0e8f2253b683078e4fcd98ba6e401e76eb7023e0217ea9fbc1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75021
the chainentry 75021
- sealed to the entry before
- 54fb608d70ee84d86a7257b97491cad86bc2a26b2006edd0a52ce0f591c5024e
- this leaf
- d8343ed77777a69122d1e193e564f49e5a113ebd1a0d70fecf651aac0d412d87
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XqIDGGphNhDGl3fyCbcK0DCy4OkrQImLtHWlNupIDVFRpju7H23qqaKrLzSdBxzqzvSphJLMjRCg/c/624PBCg==