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
- 5e6a527583dddc403f22ed1cf71139f755c3d76cbc9d4b008a1f8d3de21196a1
- request
- d621cf34c66014417b64ad93de39e26f4d3ec616bba4046a0c018ed1dbfaf99a
- transaction
- 8f1fa4f16ff64617596cce1d670fc707c2009f42c762125379808f0f2a84feb0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62374
the chainentry 62374
- sealed to the entry before
- 0c4ea10cfd00d06f8279580c8d0caacdd92febd3056e5f5fda5369858c2a58f3
- this leaf
- 2a54bfd4fece93ac76f2614a5c9c9fe82ba60c4c797329e9aad121dc742cde4a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OWP1drO9rnU5/31IzWrFaoW+e0HBWwg3r9IjZoDis3t1ud4uLVvx0oMoUyrNYIzxClSz3a+C/JuF1hudwZa4BQ==