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
- a7bce97ff2c0600d640120d0ecdfff3fc830022eaaae5940609d199f44f22668
- request
- c5323fbcaed7b77f0aacdbc2d15954eefa68a4588eacd355f8ecaff1d56ef428
- transaction
- 7296c56b3d91ea39e6a977f19552dc7f037aa6505f5d9eb95076b2a25cd064c9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3270
the chainentry 3270
- sealed to the entry before
- ea4ad55b10215bbaf8272545d4688e62c624c95ad78d7e7a6966b41004e68e1d
- this leaf
- 44b065404660e0d2f9c2188d39b31e4c2370e4bfc556a93221cad1ec5091b78d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PNT0+eTMhE+0K8VZ/ESo0kBBCxnm4NxRf9hEioxgdiVQO/XI7kkcWecIC+wPkcPjtyUnhpYONG4tSrtmwxvvBQ==