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
- 8074754783489e58f1879c9621f5eb60342c85935527707789be40ab6ef47ab5
- request
- 481379e73aafcf31a419575dc3c15157ce48f97bfe4b85edef1ad621f806fcec
- transaction
- e4293bc7ca0ca6be2ba989894daf4336d9c51d2b2861127f2eab767fe27e1e57computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59148
the chainentry 59148
- sealed to the entry before
- b02a7270e3942a9899a5843cc2f0aba0b0f80851f9922eeaf157118419aacd1d
- this leaf
- b3fb39f34d3ae64e55b447e6f16c3644bb3f1ea9bc5991e3e7a16d96a24ce94c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- whI2rV71RKbfo1kYvOs9ktKbPd1wrUuIUVUjYFicqwZ/mtznmMi5LfNU0TGqCjqItQqiJ4jMwgH9sEiGj6tADA==