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
- d997f7ad066eb963c2002036494f760c6ad35032585848d194b84e432bf3286b
- request
- 89951cdf2c0dd55ffe818be2cd4362b4cfd3fcf2d80de782a27276668b31d7bc
- transaction
- 916497360b36cecf426814d121b6b16596938e5a5c8060e35a8d857655e38b54computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13512
the chainentry 13512
- sealed to the entry before
- fd9f01069c6db61d68dfa24a7a606d90fc30b18c1da5b7e89b58feb3c5799d75
- this leaf
- c945dac5e000cb478c9e49d85efa0b995676932f6b61e348a667e6034740bc24
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jUJUQhRiA8fP58tMF3LfTWDS/WLIcP4XGdkTDor2lavdMjmU4g4j+9m7nnHBwVs0Bpyt9FxsZJ4UJJhzLL2MBA==