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
- a3803c225e1200ec118502d18428e0990bc304628f1f52c0c28a7abcfc449bca
- request
- 7e2428698898cbd2a95c8ea6ca5b6286c828e17f369ed673abc64e34fbe02ef1
- transaction
- 7573308035dc3ded01cce44f670112e1a2cf4568ba37903935e0809eb52c97c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62152
the chainentry 62152
- sealed to the entry before
- 9587cfe0526c0bc56010006f522d35611fbbe527882098b5c597e9828db8e5d5
- this leaf
- 17e29f6f8ecf13de0fdc78377bb35278b0aede9dde0424cbcc069ee11d14e94d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eiRC7EIKqPxULW0q1lZKOEME0uUCzcXNzd2/KtvMEDsvM9L5Z1DqkBH8ijiJUb/Exf9Rp1AkY0EbtgttI+n1Cg==