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
- d7c8dc91cc3698dcbfe9928b91a9da3dfffdc957ff227e04dbb7290681bd6370
- request
- c5923e5303a8d7d478bb9bbf56e6000e4cb1f98620493f662286b97948c370f8
- transaction
- 04fa913f93ebc8b05599a42532dbc9b71271600e769fc849adc2db4687bcae8acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61859
the chainentry 61859
- sealed to the entry before
- 89a1795701d7a3c2a963ba7ffecb2a027141d39df8b533e69ede0d0556c248b9
- this leaf
- b4e3c1fa32de80deba87d4071e926fab981d07bfc2fac5bc65465bb1a34ed5ad
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CM7jZWG9+AxVq58VQbJKCJLmuN3fa1GN7eoCJW+JhfZZUhN9FFggempEkdJdyfo0MZ4i19vke8XHGt1pPWV4DA==