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
- 2501f71c26e27e1f3f52d489556d677f042f807d2ae10d8ad131914dde436d85
- request
- 200ede64d8a5b9d72b9347ca0c4141688b6eebaddd8f5426a6626ae77c69b6fe
- transaction
- a24290ca526884182a7ad3b70df800170326dbd5901c75e08ada27cf4fcafdc6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41400
the chainentry 41400
- sealed to the entry before
- bec8209ab5681670e8f1d62601ef9b868cd4e466c1a52f5cb7c4606627819c88
- this leaf
- 47442b02062f899b27d0bd9f53fbbe6ac3195c9c00dc0a173d3285287fd0e976
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4catjSCTxQ+kuQLRT5UXyEiT7WZas0IUtNiP2K69sc6VOrFzJOibf43vD9iBaijVqK12AHJhJM+DKFEd7gf9CQ==