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
- 63b9ee31c695a31e1debbe19e307ce5c9f7804274dc44c55aafad773d1701e1e
- request
- 30a3dd671fa7c01f07995276d99f21c6b38c24fcb01244525861c67704fe0a43
- transaction
- 81db0b24ce5e930f436db52121a6fe5b02dbb6ba89ed776644218679e6d3277acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76904
the chainentry 76904
- sealed to the entry before
- f59136c1491158c677bc9cf64a648bba53cb386bc8c9314d18b97cca47975ce6
- this leaf
- 1c8ae29ba5398df046549c74194b73a11e4a7e684ad55e5c3f511d43cf519f23
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oeMu7dSTVyyUgHK2HjYcht8XHdLNYBijzshdvkN7IxAVYJcXGPRSiof6geBGzJW1hk9s610+8G/EdeXgaNwqDw==