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
- d9a562625deb5b6ed917743d3362a6ede84107c7b61c3e32c74bca6c6b767fb3
- request
- 55dcef3d0f47326a7681e5ffacb33a10db2902228f0942fd6f07db1d1ff8d9bb
- transaction
- 1546d98c631552b75864ce3cf6e7f1c3cb7dd1cbf36026814c0a912e2ef919b6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63439
the chainentry 63439
- sealed to the entry before
- 0b9e53475bcdb52b80298cec1f9468229ddf4eee636a4d34f7dba909f6bfc7ac
- this leaf
- b89e0849e7314c97c32f73bb65c16fa81c1cd9dc849de647e0b2ad410d285dbf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- p258zrZVI4BbKnhpMGx38CglvOcJgrMlprSkUqFa9xfeVqpNDMdER1v7MlYgxjN2kn4XsD4BkVgjrZMmZo/PAg==