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
- 0f36779f49ef6518735d9f1a9603923e1d089c06943f331ce3207b4e146b9f61
- request
- 00687867b14b13146a073e41f143c18eacf153af6f341ea613f7b606fca0f1ca
- transaction
- 78f87724d9d2537838a57017322d9a66627a4305371e4cdce3aae534be03fc2acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23757
the chainentry 23757
- sealed to the entry before
- 8cca369a7a5fe3ec430051dd4fdb99405fc6db018bd315b01c889b2fa83b1f82
- this leaf
- 0fd2848722c5dda59d2800d9c66c415c0d5bf0cdb71251f1e1ae6c2d1764348b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- e+5WTOd1qFVREkmQpnYu5FrzCO+MjRk4SjkqvS5plTjoyvf07QcTAi7oyLpCeYgnFEDo48wWaesX7KNMNRUXAw==