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
- 31d9d2e509bcad7e1307a2a5a6b01487bd5f8db3aa161188507ed402693c7f7f
- request
- 0494de46004884dae5d93b16cf32ef56c193f10e13f2eecfdc3504ebc6d10de5
- transaction
- 9fad53aa0b8dc46a904f2ce46cb848daf3b8c24ea23a8d1a594138862d8d4d68computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11737
the chainentry 11737
- sealed to the entry before
- f5391df34d89e9582028e5505917bb81189cd1d150cbb6a2b234d74d7e9b67d4
- this leaf
- 74657ceaee0853f1fe9376bfd044907e857d04484d7bafb2364b7829fe326d5e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pIQiyelVLVWW+igAPn8ZjlseyljYAguxBdHuXcaysyay5oy8aFBNQCjB1FvECkoq361so2qUtMU66O+GLr8ICg==