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
- 021cace987295a7b8e1891390b3dd34819fd89bc7d2347ba23efccd0ae3af503
- request
- 2b370fc4fce56d62a09a84cd75cc2415aececec864d76f1b6427a1a738ec9ea6
- transaction
- d841cf1f477fe3749b2ef5c6599509c19a80261f347046fa41689552284f920ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13351
the chainentry 13351
- sealed to the entry before
- e59acd1e02a2576b20df0a81832e89c3dd3a5f66df51b0f5e53c764c40b17334
- this leaf
- 4e23a014e27df866cec47eade8ce9b7f05c75facb12dcd0ef2950f4bdde52830
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- R9g35vW3SV1xu3WmAz/f5ZPxTKlQtaryvENfQfJiiygXDD2KqnYyz+Iw+DnXrhtKPxp+RFaOQSluyqvB/lUpAA==