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
- 4f92f2ee045b14419614c509261c5262849859498afb33f9a3c23bcf262c20af
- request
- 616ae816cdc5f64a6496074db014b67a42f8b8e60ef6eaea81c07b91424ee4b9
- transaction
- 8879f0232751b2d447fdde52268fe6f947a0533665570981297d0afe054ff18bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 416
the chainentry 416
- sealed to the entry before
- f2c424e6f06bf468aba7235c3ec22b03e186c2ca0ea5b45d48f9acc59d55016c
- this leaf
- 05ff02919a64c8e898aa0d0fa2b4bf38ee6179d39f340f9427b058a438dda53c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pPeLhtP2qQQOQIG4LeNKJUE4kHDrw6bdYH34f6mUjY04/D6SigN52YalGo3lYmi7vOpBSTHADYbJuKBofmsMDQ==