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
- 3c10da2e2c17cb1070b40f0005e48c8082960a369b1c529831699baaaf377c62
- request
- 257973aa218999aff0e1aa15bdc643fb89058f3e6e7115f6155fa7297d096f83
- transaction
- 8c88d7e867c6ea2ea7f51288047ae446ada3ac97b132301c6e8ba23c2a436411computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63354
the chainentry 63354
- sealed to the entry before
- 09440abb3c31d4da9604068d2c9d6c7307a3e33e0c58f3e70f76216d948f336e
- this leaf
- 5a9ec1702b18ba232df6f05123761689fd23e2382932fb1ce04315d4788c2cad
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IKTFNT2BsJDdlTTNxifgkMUP2ewzTcYxQzGPy9/hegEC+gJK/3aeywW6ehnAbjk8xa3bvYzqSDr9GbM8yfIuAg==