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
- 6a3dc23d789445c3a6323f27b94d536d5d4f2892edc4979ffa7231c0a126c686
- request
- b5cfc71a5527d41b7a9c13985b8e5aab11505fbb2a59254892309466e0bc2a0f
- transaction
- 0cc88a5b8e61c3d171df55d66fa454dede9f004387e830418148523c50fe4531computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60658
the chainentry 60658
- sealed to the entry before
- 180e4052eca08aeadaa1e1ebba3036f0f8804b17f50b6abdefed8d94d48be5f5
- this leaf
- daa95d98440562ea2bca1070eea6928711d3ba43036df9b54749145c1c7c27f7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lMiLRGQ1j4pkYvSuHgQL57qFuccqFZuvjHhHJTWu2uKZ7bMn4rapCm7VDDYeYJ5zwwgHIijfLLvwvUXjLUGeDA==