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
- bb6673a67286975ca214c86dcf750d9939ca00bdd007b242100a37ea948d3e0e
- request
- 926ce3f9af32fb11108ec73450f7e5f40173a3005cefa2ed2dac86c55cc0d016
- transaction
- f7f17c794e084b618374c1a9cfc390ee0c9721ebbe349468f2dc02fad5dbc583computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59788
the chainentry 59788
- sealed to the entry before
- a26b347838143339ef2fb898caba8599d2769ace0b058731ec30fe53bdd5fe74
- this leaf
- 4f7f0200e2e467cb88d73783af01dc550d63b43ae03a05a3e1a83dce3fd724da
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6CtHbFroOKkBMpDGPw278RkcRcIDYbRyCxaPGyDBDIjNNuPWWcyHFVwRFrWZYA70Tdpk5x+Lz8l9vLHNGNs4Dg==