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
- b7ba699afe394b4024973c601a8d04f9154a98302ad96539b3dc7a3328f531bf
- request
- 52f129aed2a0ed3ba047d1ac83c42029231ed0192b177719028f4c13e1e5badf
- transaction
- 2c957d540037ddaf6d498ef12dc915b2127996748513feae8c7360193fe8dbe5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75348
the chainentry 75348
- sealed to the entry before
- f6bcbad0180cd5c6a18bb12a163a9a80fb4e0244b0ea3d5a6d40f4a952a8376b
- this leaf
- fb512a021a529f7c8539f7fe2323c2235d8473a379599c64603c73da3156782e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RySvnegmBcRBV1hiGcW/FA519bPozpJLrefF1XWrKhad8Z7RuBwCuXrsioWW1XXLAT6GhGybmornycYGQLK2Dg==