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
- f04dba1c4d37874c1a09159a2bdd3e4f9998217a3c26f30491cec6039c65f50c
- request
- 1034ec563725dd6413c4b66d065e62e2bff838aa8eaf526051304f213ee75a7b
- transaction
- 81c472fa72916903f9099307a1e93ad1c5e5ca27bcd376d906ec5d2c0e2d43a0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66509
the chainentry 66509
- sealed to the entry before
- d4296a8eca7ea3b5cc956b32c40df5e3c7d2b0b7da6fbc3bd4243f2f5870944f
- this leaf
- 08bccdaccf8a42978ac460cf04f76383aba0370a3cc7a546f2d2ddade25b671d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NlVst5h45miHgHL60WQ6991Azlu0ztrxXDv7z//tkdXO4JewgSQO3ndwKblfAsjKv896oBXsAJOXRaokRoX3BA==