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
- 8ca7b3785e92bf78ca4b3d2f7b4dcf2629eeb7104d0cbf2f686c8a72264a4bec
- request
- abfc0b68b3e936b758d1e87f33dd022040bc4f5ed8b2ec61c3492e4019e6b276
- transaction
- 1d37dc7550ee732ee6bedd45051a00bb2743408d42923858a9b2b6364483f65acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69002
the chainentry 69002
- sealed to the entry before
- 85a404704c8a0ac41e12084787b57fc2012ab2ecbb9ce3d7d89a742863bb8f5c
- this leaf
- 48c04a31424645473968b3c26e0b13bdb1e071cfd08d03f7d3f77a8b654ba73c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gvAH3t4at9nNcPi63IRt83juAi/5q2t0rLaQC99B5Vz/hl+agWpPbuQ8eobb3ftMBVR+50y0JGf8NfXsXmShAw==