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
- a53d9bc9f929722f3b8d69db812d0f123c57cd0ebac619f3029ad505a4f32ef2
- request
- c051312e094ed50c781945607062a7b1fca120d6a5b2dd21df35397eeaa8fccb
- transaction
- 86922677df17925ef4c74a90145bedba2e966d93803e39702ad0e5f9379d14d9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76395
the chainentry 76395
- sealed to the entry before
- 428186b9ea8ce55ce6da1d02ad0f9da5ac1debf78f3e39f68be274f34e127827
- this leaf
- c9fd32a8185f64f918b1cd595ee462a05a6379f55d4f9faf8932250b38269679
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- a/mA9/kl8zUGTknD0ZS7WZJ/G19YN0pjFhKWmrhe24pky7jnq/BsI7Qun8iH+BR9b2zwaYrigSDmVduZXLPtBQ==