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
- ab9a036495db0773bdb96658ef931f16a7233f2b19d950b697ce8f0f38bb226a
- request
- 8a22c8a62093a6f0561a921e5bc9f74e9fc7307db5cdfdfd206fcd5c344126c0
- transaction
- 012b902921e7b34f0cf44fe337ed3005b9c66471178dad697f4a7350da1f26accomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58523
the chainentry 58523
- sealed to the entry before
- 19028a2616f9ef444a35923e523ce380a50454144ed4f2d78653715352c72673
- this leaf
- 901e052a237758b82eb56071561821bda14c8faaf7380f50ba4f5b1130d73842
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lK1cfK9cVYPk9oFTklE7A8zn/PAOuRw5Du5Mpowjp53SAaPmDwnBwpQn7Mswu2NqlvzL19uqvA1JX/4ZaLbkAA==