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
- 5c59e1a6d79d98b65872515b919ce58a74f560fdc91eb38eae93a0dc739f45df
- request
- 966df65e00f2d9d5e9158fb5568744dbbedae40d5d864865d902a48bf459fecb
- transaction
- 5f995ff09343a9749a0a939775d2f15be6eb9feeae2fb27984475302fce10403computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62782
the chainentry 62782
- sealed to the entry before
- 8bea492b97e9781081b2e6704f9db99fe3a00e8ce81ee6b673f051b5e01f1b4e
- this leaf
- bcafb09bc8dd23d9da40e06ccd8d6b7f2f3a302f63ae7eefcc1afd0c1910dfa0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6Ka0PRPjg8QC95YdnUR4+nJ+CJdGp/277zcmtZdZuDiXGcftXFr24XIHJEXfNI+FTJmdVNoYnQdRn4u87kZnBA==