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
- 755dcf5156de6411b9beae3dd6356e0a3de3a58ca0495b102c4f9b4a2a2cf57e
- request
- acaf55bd3c7d710962f63316b2ff14bfeb65744bfd593ad563ab82371d4ec785
- transaction
- 407f6b3444f1bbf2120075ccb21d129394455a6886630d1a83f2f75483374005computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51716
the chainentry 51716
- sealed to the entry before
- 888fa8d4b258b069c63f3e942d1823fffb3f491bc751e3e40f6cefe8cf24ee3a
- this leaf
- f9e1017ea33a88697fe546b4bf356b34039f3f65b7558003976135d709d23885
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UCiD5uMtNr7B7xmjqtVPyBOv0ySpki4x4N36oEdFbv3Pf2nyJWa2ovFxcGw0qeyXkPKhFfvZoQoOHKNEH7FMBA==