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
- a2d9482d1cb0d1d70c9b5df8cdf4bc50cd071b9f8a6d25dd25ff23fdd46e709a
- request
- c08ef25dbcd54444138f580ea5251c0c2dd391f24c070ab85d94154110dc5acb
- transaction
- d1b30a9eafb1f1a4f50a94029d62d291ade55ebce795b70c3c8dab49c7872074computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65228
the chainentry 65228
- sealed to the entry before
- 722c3d4c8525a647be822fbb49500e5ad23542874e32a138c7d85cd4796175bb
- this leaf
- 1684a856cd9a34969471bb4d1a8170f02f49685c10f659128e1bf787c8cb14a9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PI5GekAGkrWRWk3MfqT83WK8TEabrF7k4Sn7DMFYbe7bsISthsBbLzcfamfuKqEzBDn0IGsvtlSMNxgflLImAw==