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
- b84b6840bd1e1b3a3ae71d326b39c71e3815d85d3f5588440213ff42e2e71376
- request
- 4d7ae10bbcf2aedf850b6aee31a8b2b88aec5468a9e8ca3668c4bb88615196b2
- transaction
- 30d87b9dd38f93c29125d1343927eceed5614b602b582477cc27cfd067619474computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62589
the chainentry 62589
- sealed to the entry before
- 6ea97679c98a3411a8b0960ce8243f724e6121f72e57a9532027e386b8eec260
- this leaf
- 90778e6645e993ac09a3b3209f0b67dd7e5d9cec0ddb44fedd3e870afd801467
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FfuSBFI2P8/Yx6g10Sc4NUZsluK0PhrOyThkZjGraPrYP4FENnczrFTpuKY/fZoEayaazfP4jAgjj585hd/UCA==