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
- 7775e370239327fe1c3ff36268dda13d6d7449d1514d0942712ebe52ee028550
- request
- 0cfd6b55455e4861e589575f97cc68ca954ef1ee8d2fd6ebe4550c2ee2996780
- transaction
- 4fe27fec4a946808da83246bdfa1946c7952ec2952fe1c3ee86cacb58744fa82computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12958
the chainentry 12958
- sealed to the entry before
- c64cbfb9f1ebc37eafaf728a2290c4802fedb343a6e7df535e888496174e54f7
- this leaf
- cc3e357c3130b5044684634ecc8a9d2cb932c9b683d46450aff6cb887a998cc5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ko0fW1cQfTYG+PqiO8ChUKhHe+Spy2AF7yTQMy8ExBSlatRLwFxa4LtN1QPdOupD8MXrjT0YuXSYqD1+D51xBQ==