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
- 14db8e8854980dd147424a0a0013c9f79175ee4d986e0c6654d7ee42a9f5ef3a
- request
- 7ebaedd3b3ced7f5a275993884848f1b73ba8c42afa9eaeec7b24ec1fdf0749b
- transaction
- 6fd8e1daa838a600566a1d795e1ee5d44b4c365cdc3c31bcf585f076a839102dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20495
the chainentry 20495
- sealed to the entry before
- 9b87e4c9b34e000bc1b1771a62f7e3403f6a90dceaea24b2c2c0a8f30306f1ca
- this leaf
- ca5300fb49c253d5514d83e57691b05b62f3b5bd3aa089385d53894a63b63e01
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2c0RKF4id4lw3Q+LDkiGlFYU6RKtERP/kmqy/L5m1X96OgsWxCkuA17bM+O5JgndTTbCvWckn/VUxk9ezE3SBA==