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
- e727ff08df7995c4f1b27e9f333d8ff3e38dbd739e3b4fcb04350d824e8a074d
- request
- 3e10af4123b97fc3db314c6d19e790b5a599bfbfff88ffa2016d2e605efe2cc7
- transaction
- d708e6d0961b95a6bfcee4f02673520970d6286f80e6466d04b2bab07c69cd5ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32788
the chainentry 32788
- sealed to the entry before
- 98691e0055ef2c4731dfcd017a8c982a459935c89e0eb850fe77ac48b93b1e62
- this leaf
- 82663fbd5e2c93a06b55803d9bc2cf62ed827f766f122bcac421a15cce43ceb9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ea3TtzluZ8TCMEjQUXZl+2G50yKFtG5TLCyKftvRcyN7DNAh5RTOSZQXvklGf/KiNoIkyJXpDbHhQJwl2cSNBg==