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
- 70f9553935f7f01a73acaf43cae8bec7a53cc38cd09e30ad33498e6cc4545ab2
- request
- b43af87f02ceb56299fbdf0ac85a77420a3026a9697725a0c17672ca3bec7ecc
- transaction
- 02c395c62a3443d0c98818c2c15fb7f9820b8f166292ab5bac46dd6e69588bdccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44439
the chainentry 44439
- sealed to the entry before
- 8e5a25050a3f89dbd22544d8bffc90d94eec9d0705b0fc12fee3b82343b7cb60
- this leaf
- b14be160f435eadc392877083cae3b66196c846dda1e94e1a14624b13bb4eaff
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1yFu9Qq27HiuyoxhjJZoIwESKb9rhAVmRokqzc+BWwt7AkVVCuRmJBC1jyf39qopfMwGAukeAm6i8aE0BNR3DQ==