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
- 3b0f4f6dc911bd48e7b1957a2bd5e03f20a70c881b96590d9b8f36095bba2574
- request
- cb451c0f03b4d4c78df73661905043b75ffdfe0a4ee061d6f4b0e9ccaf2d3ccd
- transaction
- 013d526f699240e93339f3e2c03fe152ef8a7f2e27db0d38740bc4a4edbd720fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 606
the chainentry 606
- sealed to the entry before
- c1b39aafb7b555a2071fc5f33d31e9cae30213687118c5f462ec16f90c84b275
- this leaf
- 3d0756166b1486c7c4db12451369976ccfa213c03d733c1c08cc00c9f6b8aecd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MpaYkqCjhqjk4BClQqpdOICsOLHHd3dVq//8QsA52ySeDso9sQuD+YCVqn2La0EgxzeusCxjCIPY+j/sUqmUBA==