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
- 082b32568ffe2386e5a4ee71e1426d2649153021a3595e36222bac0e4da5a02d
- request
- db78588ee92c298fd710e7ff29f44bebde6457f677120c141b5bdd8cb930e675
- transaction
- e8dbeb4c7a677072c1691f0c3e3b50da974e152f9bb4d9ed322d0fcdbe2037e3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18363
the chainentry 18363
- sealed to the entry before
- 88741068e8d11b7e2797f1221d4026ca4ea741c3a5e2851ba1e78eb471df8332
- this leaf
- 1618b62a8b96f1868bf4330fe28a79c8cf7b3554bf4f72d66a58bc64f5c0a99a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vrboBQ0lygfewAWA4WtzhdKPKCCk+gaHrWoplBB7NehpCb8wtZdiGe0Vbq0zlvMcdfgG+k5WlpjBgk/bvHg6Dw==