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
- 426f95644da9c968607982df655b11dc18f9f9dd215740b1c9608b856a2031c7
- request
- 6703f6312eca0c28d030fd6fac529dfb653d4f53456d1cc6456b3d24020c1522
- transaction
- 7e49ee66202c739c02bc4d5b9f371334b047893d156b2b07be804d81061f0024computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52715
the chainentry 52715
- sealed to the entry before
- 0dac14f353a3ccae3397290a670f8f3c8189af65b8d4b1583c9b7764351ddad4
- this leaf
- e19cb4792dcda3f5d867cc24d432d38785319eb470d7c73008eed0515c6f3cba
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- C+1GWxVjHudzERJTKiSlC5lql1FzJuFO7Eoi2FGgq1Ci5NHjrK7F3S8mYWGCBj7ScQDgLy8Gs45D8k4cy0BsAA==