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
- 72e4dd7853fb62d4df90d2169d363237e46f3db4c39e104734bb53a147b41a08
- request
- 5230762fa714ccdbc03459bd821b4322b6257485826ab93e8155062cad792d5a
- transaction
- b0e440a96df9b2a68bef3f5ba07e8495e18496e46d03aaf21442996db97b82b8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59421
the chainentry 59421
- sealed to the entry before
- ab03d5d5d96142cb3c95409550d08774f0cedee79bbb95dc57bdbfca09008b6a
- this leaf
- 190a891ce6d0e20b6acd3eafe2a1c6422e3c15073987cdc128ae51feec8fe0da
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- u+FQI37wcl2NeEAcAcl+gVVf2hCeZZZqGAR8OxwFBwAMmza3oDuH4svACprXOCPrFpRthXtw7bJZZTB9Pkl+DA==