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
- 58b842c13242768505514a0597125a8550f5060abf41d95fd31de51cf207222c
- request
- 2f421b1c3706fe264b0238df4ba26ba6efb7faa511306da4466b05f2464fb195
- transaction
- 335cf1d9f500b9590e0d5e70ca39f259c32a686e4439fdcefc8d786bda3f3772computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73748
the chainentry 73748
- sealed to the entry before
- 9d0e1052cb04e5dc707c90ad4522578a00bd8ea370e811b397bcb374c5a5e368
- this leaf
- a13fafe012637e561353fd65c8f8d6862e442701924e74ef862fa9ae68856486
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rnjel3kZkSOAxDsXXKRkdWv7la/NY5G/JRbxYmdf8Esbb7IdIXHJYHjQ0KQh1Wg+A5RlmeQ5TQJ9SsKqxFSEDg==