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
- 9701dd1ea326068140fa47e4421a00bff4c6576ba512b343f865bdfceb8ec3f9
- request
- a0169506145d59f71d7a20de57b3e4f5d42c06d2f7cc840114ca8c77636d9b87
- transaction
- 18ee5fe98b99c633fba8bbf32683b3fb41b6a463553ff507b0967d8460bdcfddcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36506
the chainentry 36506
- sealed to the entry before
- d41878f4324b7e94a5ffadc89d6d028baf871d5e5c19a77f06a6c6393c45229e
- this leaf
- ac996690b7a63d5ccf549a66e6553acc813affdff54031956be66b3217c49f09
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Emv82jSTzRnQVyqAKYhQOp784tlMUFrEQyvO16/PEnaU66/2vQOi6a4XUGe6rJOixmAMd2S/hhKJEmZcuFNbAw==