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
- 095a55f9ae4ae6c4b4ffa8f3d69fe36984c50c7b922b33809e68e01f7392b1ae
- request
- dcab27a5f8476808265da11443b5933eac1458bed9d4113e78aecb064df8d0de
- transaction
- 0f17fe737f7cf49882ac7405c0eccd752a74229a9dfb7651249480387fd3536fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4808
the chainentry 4808
- sealed to the entry before
- 971623bc322026beea68702853f8b21d3f28244dcbd4fdf0985d6851a1f85e61
- this leaf
- fea1bb8bb9f429a75b914bb509906284d1264231a8f9e157d085e268583b0151
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kfXaJA+xKKTRgGCSOaOsAqvpVPiub0atWaLeXUEmsZlVEwETRj4eUmlNG5Ig/rSpX+Pv433mnpGiq9fSTwndCg==