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
- b2164e43dbd6449ad3779a8e7f6da727c94e5ad583d22c6decceea89af8f46be
- request
- 2bce31f344cdc894f82f63b0f2e4a86f87075ce94cbc299663f982c8090bcce3
- transaction
- 3da00fd84b4e9c8cf294886072971d132dfba70bdb6af0583bfefce116339542computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47603
the chainentry 47603
- sealed to the entry before
- f054b3cdd1f515bcaea3a79f929802350a7a2e0b488d04077d962235fd489f6f
- this leaf
- 5fceb05d8a917b9f2b57d58b22ff6b592633beb5af4afc468d85df4c037af024
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yGrzaajojGfHgvHTYb/7A0Cqnqe3tt8L3zQ7G++uYr9owfZYztdKHh9ZHAPkAsUf3GxTUI+mel42Q4stZL8vCQ==