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
- ee4b5a8b9510ba095fabee83358a46cdb6d54810d76fd197067fd4ed40ab6ca0
- request
- 9df3c44a6a0141c96bfb46da13aed7827ae89f496002fb45a2338c3ffa948254
- transaction
- 35abf708ec0cc7963bef1a0eb7bfdf4a7231a76b50b8d41e0bc960b01df553edcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1555
the chainentry 1555
- sealed to the entry before
- 0ed2607f8b2dc002f259113c452411e707340edb840a4795fa553566e973e93b
- this leaf
- 63e4919795bb0622f903e7ba7ceb128681fdfa09980c3b6da7bc2f2817e61ff0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- q771MKbyPErg40D/HhqR522ykoNJxC4BaOcg36TSwpSNH82Co/zjdCVYSQUs8QBW6A2QNW4MRrIy4FRW47k0Dg==