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
- e9870365e256b23435470adc06b87db6be3ebedcc2906eb3c2fc01244323f4e0
- request
- 028b5ba7a1efcdef9376196d9c459f3a3483174f08ca8ace851bc772878203cd
- transaction
- e093905930780bff109de7208f3c9ef5b93a387380d681c90e62818ca27f37c5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34588
the chainentry 34588
- sealed to the entry before
- 3cf8a36ba83b4aab97e80ea03e05e947dff3e98bf343b4c750dd38902f2a7639
- this leaf
- 884f6042e471aceb2d9254d9ce6b1abe4a664bd4fcfd4688be6d3a261a447455
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HZ0oyk/zqTe7XKi0aOKlx/1X5aqqWyT+2e1yIRfKP8D6Q62sxXC5IjwNU3fAfYn29Kw7g6VkiTHEmeW4OAQOAA==