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
- f0793a545e3dc4f5238bf531454dd4e66eef05604bb3fc76b8572c4277439a39
- request
- 3e91e9db7a766445e0add2d1a77157198fe6cb5bd0a3dfaae7af26f8aeac9420
- transaction
- 275d29970faaaaaed09a0e1c0d0e1ea679b575c3ee4ed854cd1fc227c81d97f9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50737
the chainentry 50737
- sealed to the entry before
- 02ea4299f68438bb622c5ef346869bf8e8d9f4e524f50295eb438f5b012eee85
- this leaf
- 5464e4c99c834eb79d972c93a715ce744f50a2214c8cd5d5f34208b1d9d9f4d6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- K3oPEpGc9N/xZvVFi4kc7kcIgqnL5KuoAKSXaKObACINHIHwrJF128TBVJFVXlTbybZphsu8UaSGP84HM1VuCg==