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
- ab65ad7326477e9095eb53d47ab05048909894ff6763f80effd9d5dbad418ad5
- request
- 3976a80d2f220998ec09488e232085f2c7886b36ea91f1f23587e99b88492153
- transaction
- 2ff9073808b372867019ac0e5a9185e34a5e1e5558a34c8277ad8bdc2662e2a3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22469
the chainentry 22469
- sealed to the entry before
- ee38814945712bb842efe7687723164740b8aae7c5d84427f8db411f8e7d8e10
- this leaf
- eb2dbb7b5a8f4edb9658c177158c92517cf948fd9fbfb8d7a74b85d840da96f5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gIBvPWHbbcCKCVv+Muh6AN5PwexIKBXm6Sdt37aVIyYyeX/dR7g/LM1Uc5psBJc39e0Nqs19PrTbDO8ojei1Dw==