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
- edf1a2418f765c09adf8ec6e762492ae0096886903666275e46341b4e2bdece0
- request
- cee24f5e17c64bc57354dbe446e003d5eb912749cf1a5fa92421c90e5d333385
- transaction
- fd475d6d92b6715a80af0354f3201c7028142d36962bd97f1bc16d36e83317f6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28439
the chainentry 28439
- sealed to the entry before
- 0e44e0172c1744620ea86ea9cc7fd417ff577774373025de2bd138c1cb9a6f31
- this leaf
- e1d1431f1841c645c0e2e7b80b6dbd44a02a7436752ffe4ae95ae6365b3c5939
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wWbSloldTRE857ngpN7WSLjLrfyrE9rhJGMY1cEFXZhH7FCfaNVMJJlhHh4BY98dc5kfjev7IriNekrIYn78Cg==