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
- 044be41306f2b81648eac3b7f3bc5172b7db2c12d02e0b1f3636107272b9a961
- request
- 9f2b2d1430287c364e7c9a7bc8c498fb77d7be1aa4602e67ebee4df9e176924f
- transaction
- 65087293878496af608396e7b5f2c2fd57cd74cda055de5364282916a4dcce70computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40661
the chainentry 40661
- sealed to the entry before
- 3aa9459e025f7c42357f1a639f1b3ca913983ad61185e7a258f5ed510821c511
- this leaf
- 8f6ab011838c8ce748ce3fe978299c90a32ab29cca7d7b3016f05c5c8cbd1586
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Dvqvuea2Yk05+tTpiDphnciB07qjUdNvUPZ3jPFSN8kuKikBcBP74SmdSN7GmHKXr5Qvlu5lBXxRgv0i8RA9Ag==