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
- ce4636bca0e33bdc54e21e230e30fbbc7d970848875b722c51b318a4f5cbdc29
- request
- 275edb88f640fe6c04251d9d152e00ac46ac820e4422606a24f6a70b29ca84c5
- transaction
- c8e97029e6f58bf860bcdc5c97cf242d9bb52f5886ffb7d4f2c4c716d876e64bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6049
the chainentry 6049
- sealed to the entry before
- 18112b43121a2b73649b79171cfe9d97ebf8f287e13ebe9d5b8131a62b2709f9
- this leaf
- 2ec03cd70623d740c75dd7c42a15fd31328af8946af6fa85fb6f50b90f291567
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rrbTngn/15xatd0RLQ8GAG2gizx5JcKkdnOLF+yNQN1IDQmRs7oNrMrPDVSDasGR9xNR7dJ68VL82D6dyGhvAA==