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
- 8f7ec05dbbc0215ecd6abc2f020a56584a4bab4869c0933fd6ed4958d0e24eb8
- request
- fbf65cc376659fe3e7ef96dd8d750c144920a094f2867eaadb0849be4906737d
- transaction
- cc1874a5325fc7d9042a936af85fc7adf369f7f27bc6d54988139d1a4e084b8fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44607
the chainentry 44607
- sealed to the entry before
- efb0d903e7b5dfd3c2d445dd59169a0ccb533513856f1c4dfe2367e356fbfbee
- this leaf
- b63474311cb7115d9951fb78cf9c594741ae074f54074eb6563dd575642f9439
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3lRIW8bH+zgbJ21N8wWo2DjSJCSbc0+xbLdSy4YaUyzHa2woRcA6VL9wae/GnXciwqO1Wafp9kOLk/ZTrgCeAA==