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
- ddbf24cf154c8042408d5475e31cdb989c32a9203fe8b132ed06acf9428957a8
- request
- 2039ee6226369305ad4afb5a0018b86ea9aefa50e6f326b387e431709fc2d676
- transaction
- 9ec88693ecba1ba561b50a5cd6a841b4153d31542eb5a8186f5b88c9f945e514computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30434
the chainentry 30434
- sealed to the entry before
- 2e6256b47bc03a32f54c1dcbf9ec36230f3bebf09ee7f56b0ae248d21ca55da1
- this leaf
- 46849903e78a48801e360def0b9a42d2a859d344a764841cbee9567b8b0b20af
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wQNxQhaG1QJtLr9u7mr8df/BtODg7kgYPZXNND0CexYMF2m/Kiz6RDUtXFAvimWNEOReS/zbjZAF73e+VL8ECg==