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
- 19ad6b87072e3cae4e27704ed5bbc4106cfcafa20e9db5a14a4b5b5880656e7f
- request
- c9dd34359d29c027c5e9b0b89943eae95dec1a4d15279008781208787f7f91de
- transaction
- e4c052820e1c371b3c8958592e632516f153d5ad90df89eee671b44af268f498computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53646
the chainentry 53646
- sealed to the entry before
- 2b6440dd85870377569910e99c5c9d3345335f612d9c64d2d5c198ee7ea8fbad
- this leaf
- f217173d6f286abadcfdacc5e94aa105f4efa254f03180c866742bfb286d629f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ABXwDDZcmjOsSDvif/ZoUoyUzHwG4ScrvK4S63vWCyp1UAF2sUX80nc1qM1zGKiFwBsRqkiHUB3tFTQPWBGgDw==