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
- dbc15e51557390fd86fedc3f8f42a1bd45be7b4c1524eb17faf3e526d401596a
- request
- 842f54daef48b519e5509c018ed05861c4aabd78e4537ab3d2b55b0de9bc4de8
- transaction
- 444ad5d5828cd8fd2673231d73e12731b13472ceefb90bb29bcc205bdadb955bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41469
the chainentry 41469
- sealed to the entry before
- 214f8a84b79a8a9f4dbeb0dd5a7a9db10a8a3f8a21e12d6fb3ff7234f21c90fd
- this leaf
- 38e775341811352c2901ed0a22220bba33831515bd7500607880fa3449bfaafd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hQrv59jxmIc9txyo+mwA+naMkTrUO88b3f/MAbtnxAQi4xJtpKwsGWZhcLfcGaItmdNCc4TflVek0Ij/fMTXBw==