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
- dcfcb1958e8aad1f1ce1ac2276408fb3c47c7ea9e0862d173b49398b734cfbba
- request
- 4479d1148b58df30e485adde9c5dce77d5dc319dd2623e6d34fce45bf0dc0d29
- transaction
- 01e8a334008273d78a9eb2966dbbb17a38927f95cb386fd1b7b2d07910808da5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1630
the chainentry 1630
- sealed to the entry before
- 28e0ec9bce5125ccde3e824a78f9dc925516dc07dbb584ddf9ad26ffedd23ddf
- this leaf
- 651deb01bbc4de2fb3bbb53a60e9afd5706fe701c03352a47a5fd54e1cefe89f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7X7OhYoo53QKkHd+dBS1GAfZpmzVC8rx4hrLynPFERv45iz0ztEO9ooIKWFzFONPLtaGKVbzeGPbikYRIqoaBw==