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
- 972616402a9c9b88e6095caf69a47592224c9bb71f0745b68bfe1bc0ea52fc19
- request
- 8c3666d4038c6d96fd4d9729e28195bb9587fd7dd2d3e8c7a22ac62fc9876f8c
- transaction
- 33143fedd7fac3692ee0af7e047a1951a1d48716586a57c282b4e537ab5ef6a3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73463
the chainentry 73463
- sealed to the entry before
- 639831c54c86c17e0ce18f6f3cb5a4c2268f5fca4f43ee8ebb03ad3b96d2984b
- this leaf
- b08e6edfa55f880233da1100b35756a4a4824b8e8bffd4f8507fc8c6c4adca84
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1XJdN7H/HA2reqaw8Qxycjsl5mBwDgPUJ+paKWMJIkm5YT3HAwk0/lNvboBu1zZtLeTX5iVWTNgZyFQwvx9fCg==