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
- 0df8b1c2daa4c4884090b03a1f6bbd2e6e5a9981fa98f1ea23e0e6b79108edf4
- request
- 016b53ab022c997829dc070743a5bf0fdb0cf917a103f0ae9bc7719499dffe27
- transaction
- 8625e1543e4e86ba029b78dacc9ec6333699bcf2203f7cf6cfa3873766c87c12computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45673
the chainentry 45673
- sealed to the entry before
- 1566a0bfcbd835ab551c9ea1331258cbe211da243d725fb6e28c49fb9f72d2a4
- this leaf
- e159c6ff5ee69197eaf5c7dd8d499d5c4df2eeaabc6e9e16221e6af86fa2d1a7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Z/gzTLs+3ebwRjVSGCUqeqAhsvmbGno50gAPHvVd7vR1HJQUoPWKytYY5q7yA7CjpYLHPasbKywzJH6/ZDAoBA==