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
- 8fd4c37712f3cdfc37f16f457bfe2b3ab0b446a7092d82b45fa172ea2779e047
- request
- 5ddee42c405f7c0666f41915a48a06921799706dff29c3e3f2f424b6ecfb50ca
- transaction
- cba57a6a11ebaa3687823056aac2faa7a74d35ae57b656669d6f17e1d310a7f4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9102
the chainentry 9102
- sealed to the entry before
- dbdc01e01752916139782ea605f3cc0ffd8a976e42aeba313de976ce8b1077c1
- this leaf
- bccd86f2cd88f08c873543e092f5551e4d5c1a81b6607e2b4f63083cc895b400
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cfbBa92yrqnPZRU7jN92AeYZxoY8AqnRblWHU3QU/PyApv2HWZIRVrjkVv8GRbh20eTdaXaWQQdJoXpmKRY1DA==