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
- ce7509c50c1f020ba9db68dddbd016c6303c64153f45c3c743189591880b6732
- request
- 7e246426a182d86a7159d86586fa04ae643028900ec37127718c42d37833a361
- transaction
- 148d50456d2ad317193db7d06df5967e6648792c51b8178b31aca89cce628f54computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20583
the chainentry 20583
- sealed to the entry before
- 3cc44f62b83ce988cab75cded8addc896ea9479fff8e4a684ef106ed8b975ec0
- this leaf
- b17827d0f79e55da8a170644cff2ba962c37161136275b1787a1cbb48a3832ab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Hk5Nqz9wqi9PKR73K0x2korkOZV1+tEP3qqnUrwnW7noLFMwpJGhiIfZnd+ijGI1Maqw8OJkovlq/DRYxvgkDg==