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
- 41ef093102371accece9bdadb1720915045ba6e8a9d065ee875a4b004c5507e1
- request
- 32fc0b2b851214007aec2c9845e17affeaf4e47d2af960624eeaf2f28020f079
- transaction
- 745b46fc34a90d59445f2d6964c4d1cba2f4f49e3eb8e49edb2774b29041bda6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41204
the chainentry 41204
- sealed to the entry before
- da6cf7738524f2560fb133df9927e2ddf6180ab32de08428388045eaf36d9e9a
- this leaf
- dcc07c56ddd373476668ee2fc2ebe9297f7eaf14745bc9a7884bab4e02e1cc27
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- a+qbkoZxGF4y9xD+mWNjT6DNf6aadrGxSQs+sh2bynZhct2LmYZcX45PesFSEyLB0ta29C3Zfqdllyk7hsyNAA==