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
- 194fbfe42cd5f81256b706ecbe806e6959dc5c56bd3480188a2189df4ebfe711
- request
- 439cd195ff55bf34e1c17a9040525666e76b275a539898f7299406e5211038d6
- transaction
- 30c111765b57a26f942212c08d76ee5ee2082091f934b27d3d4425b6dcde11eecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41429
the chainentry 41429
- sealed to the entry before
- 065b2a15b630963c1755b3ed0b249f7c5dcdf17d48d447e6f6a42b49964ba275
- this leaf
- 849656ebfaa1a0c5aa7d0a77cc7948a302fb330a1f981a9b2313f9ee2d04e25c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- H5aUg7F6OTMkxdIyV/QWsX6EpHEZK+gvIVomQ9Os7rgJq7nrlBELE/90CEYHSIOiVyrwZ3enwLm+UPDy/fMcAw==