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
- 4453e94c93a05aca0261d91b4c8149b8fe5a398761161a4e00108491745dd826
- request
- aa510336486ca6e48239cd05b46ac0082ac94988d478462278a3af08323baa65
- transaction
- 52d534cd443e44f54e70b0ad8aa4e40ed56406c15d63336097900c20faecbfc3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69716
the chainentry 69716
- sealed to the entry before
- 29ee55491d13a0d8f11afe4296384f3623f667dec4e72cd09768da147a6224a2
- this leaf
- 7ebe90dc42f6412c10f5d08be8409d4e73f059571df5006008ceefe8c2fc5a2c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Nr1d6EZg7dfJEtDvLQ28ZfzejZM1OV9veVZlngvKBywjJHOjYQpbwSq2ewzaQRkZeA0MeIA0m3wkbOL+cIKUBQ==