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
- 3a90c53c74eb27e2c115fbae61584f8068a8a4837ab9c866700b551860088586
- request
- 025bf93a03e2a4e2ed4685bd988db5a31153f94a9c6157bde25a409f58f7836a
- transaction
- d8eed586e05ce1e68684acb8dcafc4cd1fd3b023388563ae824d04235fe6e953computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26915
the chainentry 26915
- sealed to the entry before
- 30528ca67fdf217190ead22743fc2202e74513d318d9e1cbbe34573a429a2346
- this leaf
- 5b5c3b02ffa1202db10f4abe4a4ee1358ed3b34f30d72d5870cabbb2ee5eb3bf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uB9grJyoWojRf+X0zGczOJRqqUIXgHjUZdqjGDh2rCqnrTQi75kAhKivrPFH2NgLVDmI7TOFedcS7g3MD1DnDQ==