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
- 61bfa5d02251ede98b7331c77dda8ac1aa43df2f2d9b1b898ee71e581a7dd515
- request
- 48c536175bf4840b16d8ff31c1d1b76d179afbef551b49460fce23845d1320c0
- transaction
- 937c518c16373fe73138859d9437322fa7aeb71b3d7b503c7409392db3851007computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18404
the chainentry 18404
- sealed to the entry before
- 6bc51654a8c6f9ee5a4669025280322214e6a86317e7a381a63d0c31201be15e
- this leaf
- 925be6ab9cf0d4f6443672099f9e69ddf9ef2f256300f07653dd29f1964affb8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mwwAIBUhFD0TC1+oKIvdAKfyzsURKmwS9kVNSttIVpsqHa+TMlH8y3qP8Q8hm6EImdAgL5vivCh7bQZZK1IUBQ==