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
- 82d369362a7c8821fb5f9348406ae18aee42ef7d31e9214ac7a666158880d1d9
- request
- 308631dd18026dacaeb4f38f991a69dd2278db37c701602c7edcd79e2a2c823a
- transaction
- 46ee790427b645dd24b6715d0aa88be37b6ac5c24bc62d9e5688fd3d8e9eae42computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72672
the chainentry 72672
- sealed to the entry before
- 2fec52e3d27aae7faa467f18e364b2df1c76fbd97d03bfdf1d15739563735d27
- this leaf
- c4413993cec15ed8aef342b181279e9b2158fff2899ceec1f9aad85312d8ad69
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uuiDcEhxGb9ZOeYMT+bqy6LgauNYB3Lj9LKJlxp/vjdHLT3Q8Ickn3vK4O96FB1BrjpBPyerINZ+2RzEeKABAQ==