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
- 2b343a93b7a06ba2e6d13002020206500654ddde38878778e0774d0e773fd9f9
- request
- e2ab3a7904639d29fb393bc9e7624e9d0ca57f97e6ed27ddc3fdba4394d413db
- transaction
- 65deb74c8f000c729735cd2af92e4aed608d4fa024506e743ca9a4e08f7fcf97computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77411
the chainentry 77411
- sealed to the entry before
- d01143806332186ae0bc4d98edd03cf635ab11745011f5d87a91b4676b8380c2
- this leaf
- 7b929779552d338c5536c3f75664ca793f7a3f383a152a7aa2a6ee68eac305a8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- F8GpANvqIult80cBJa0FHhxGZLu4rP0RqPKuEZB+jjYVpzhrNMFqIBVTpgOvbdcbBQqsTW0AY6zHGoVldLSvCA==