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
- 222dfe63313f99f0907cdc67e66b0f2d3372f9ba0be05e559291a9662af5a5c2
- request
- 87c828cee0455ed4657412e0ca8e845d3c51327be6e43cfb8446814172e4cb42
- transaction
- 3b0e86db1b0c7804e1ba17e89c27318ee2d216c291dc989700d43307a4ce1468computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14799
the chainentry 14799
- sealed to the entry before
- 21569ba837a8461fee742b57e538b5a6445b9f0651d08f94e826cc013c5a9e14
- this leaf
- 317360314f7e39f49ebcf70e461e07de20ff056223b1f5bfa238c0b867621d2e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- in+mC7NUK5+To4Yxti7DyAdN+sgG2j70QliPgSDNXL1AD/JId58mTpOBewEbzBJpW/mcMsD77Rajp8lmGuE2DA==