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
- 6b56114763e6577ae0160d56178b30e18c2b20b5af3ec71810af1657cae587bb
- request
- 7efd82e62d89f8f0a6fd81eb98cdb03e13708494cb2aa5a2d1f407b7529d0cfb
- transaction
- 82e352a12da833feac4879ec0bdbe0e868d97f05f80e31c24fbab7f267cfffc8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31818
the chainentry 31818
- sealed to the entry before
- 21b66215631c24948b838088707f07cfe1568377e34c6a6821b7d598dc3944d4
- this leaf
- 7e3d22110a5e553c653cb7c1f649296989c53f63149ebcfc84957417e4cb0dca
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WCHPispU44Oh47vMSLpVp96MRquiiVfTMO3hNvPIGCarbD4090To/PGrRDFrZnRThAK6skLDKfxf56B3si5xAQ==