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
- 2438dbe74bba80ef14a71a2eeb88c566c120da937b280908f538a79b166c426e
- request
- 3057e8711e3f22c7ce838ceb8198612b6aabb7982788acbf7a4fefd4604d797d
- transaction
- e7fab62cb8ff70fbd982cb0d793d9a3590d6f68337137aec51dd968fedc32e19computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31055
the chainentry 31055
- sealed to the entry before
- 4671d64f6f146faa7d695c1b4135c7da3a869c1d20a1fd292028c5473340003b
- this leaf
- cb86299bde025c4e8b54207f74cd09ba8caac55561a73c5ef464898447372654
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oiaQoZwTYZN8RpAuML44E6sILvjXZXo+mpzvDw81Wr7paE5czlKBjeVCL3Yq5faKHFtBqB0fkbiYculSCsdkDg==