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
- b50833bb2dc7260e2cbe950af553244b6f83bcb971ccbda32d6b8bd2b041475b
- request
- 25ea3f6361d9313285115d64509d1315a94bc186477be7cc469a2d305133bed9
- transaction
- 40f4be1b53077a8d47399f5c2b1b5046a6d481a1c90e97662158fa35e53ff5d2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32896
the chainentry 32896
- sealed to the entry before
- fc8a9a80af55959795a1bec49efaab955008aac0ae776d04e8e3cc2124aa8765
- this leaf
- 64c3d7aa1c8c6bb7d2a305e6be5b90672c26191bb391e5b3bcf9c0f08b6a1096
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- l01Rki18yrAL2aHTbHbi9hFUrcdSZZSTWnADbWCiLVP5G5KfOdSfqmpCQjMq34nf0mQ3xC3w7xuX7vFcXPLJBA==