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
- 1df88d3c35d3970e7132908718b3b018074388515fcadd30362bf9b3b600140c
- request
- d14da7209913cd254c5684c327e14cea8affc2a2850956022c74aa38b788a1f7
- transaction
- 9c7474f58265118bf94088841e617eb7260421dcabf9015ae70356bd059414facomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40982
the chainentry 40982
- sealed to the entry before
- 9603f7c359dc8266481368ec48a0ff449c3e98dad099e250e0f1d1bd874aea92
- this leaf
- c501c3bbb8715c7b14c9b58dd2236a430a8ffa034847fb9351456c92aebb590d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 15s9dteACH0C/25VIoLuXoqyuyXqsa4/kaooI+a38fIVvi6JI+g0x47y0r5whJ8zvPvxOk3qnZYxzFIGnsk3DQ==