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
- 5a40059232f11c9d21a40fd861e239cb32ec74f5eb831994e3ed20dc913d606a
- request
- 57520cfed838703f63f1a98204bff62d737d39e74c53192e0c56c5a139a34260
- transaction
- 1ac9425748576368acff18a53eefabb39450b2f93814ea871332838430e56d31computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70953
the chainentry 70953
- sealed to the entry before
- f5dbd58bc4d45cda365e1678fd0a51f9a78fb170ca989b866f6e7f0316f0f5b8
- this leaf
- 0a4379928bb166ad02dae1a0648265c72a79ad0d4b7a60b036066de87a4b1742
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- s9rPQc91G5obKaIglMB+0B4phYYyYRi/09d6ZwfKaVkaghuFOaZ25U+8DIpxEbRJDYRwZpXfZXJJaHWPd43zDg==