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
- 783f858ed00fc20110cb6196e023e4c8c5464d2d1adb68fc64e541e87eb41261
- request
- dda95ceb108ee079bcafb908fd0d807593d0ce05266ac7b5d2c90446788142f3
- transaction
- 2ccd80c1507814e977a3b4fc54e1e7fab7dc56426a16da49c2d9f46627133fa7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30594
the chainentry 30594
- sealed to the entry before
- 37f2b94ad8fdf8f2ca39ee7e39919db4a9589fb7a6f968532dd8e621753f5286
- this leaf
- 1ecf023d5d9aa920970f2bfaab026a429cd790784bf3fa83a1fb29a612a2c24a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ClpL8DZhy9KYPLC0Unf2yJCOUGiVU0HyvGyFYJU1+Wxfy2UHk33oStnCx7mIW0cpIKrWIdUev002OgPgnyohCw==