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
- 95736473c28ae296e6f058e962bd55e74a64b910beb2d122b669c6a5cd6414dd
- request
- 2640af9baebcb7d072a19adb0c589d7d718e8850e4ba144d0792c062de49a39a
- transaction
- d588d4813c90ceec713883031e8d91275697351c0d13ad604242935350254652computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34108
the chainentry 34108
- sealed to the entry before
- 720c19c433dc2692211c0ad9cc5e6e4479df90a9e03379b40394aa8d84dd981f
- this leaf
- b26b1ab7f137c582d179189e12d72726e237b0ffefd1b9ca06541cf9ba8a9712
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hR8Mu0bkbQnEICfYItnofzTDPw8Z8vmbmoWKrSvBeAyrLMyXfUb2DY/aFZlR03xOwDS9vvk1pSjxbsyvA+3RDw==