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
- f4f3ac694bda840168068359d6cbd6afc87572ada3c996425dd254078a509ce9
- request
- d71b255055129b8f360e677fdd2db2b7121a094b92cd1bb51f1047529cca673e
- transaction
- 79b5eac8e9654317945634c9000e99abfd9b5ef5cd1c077e65f3ecafdedec991computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5948
the chainentry 5948
- sealed to the entry before
- 0d189f9d698425e173a0a1701f575e229a87a0f1241269d760671d95a12bca91
- this leaf
- b308d36054d0031df9477a5f924af90a17a87f68357de2b483ac305420e9b6df
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- E8GtLwz0t7hqOFFnKgiYF4duAGJB+vf/NYnuvOH6mpgn7XNlhOInnn5eJ/J2A3b1UMzeR2TnvCji1HqaOt+HAg==