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
- d4a32368457bc894f06e25d27bb8754c98ebcd96ca6b36706b852e857872a055
- request
- a507b3e6ebdb6da77b2b5ad963be624fddfefa36b78221269e2c5c6dd8d2d60a
- transaction
- 69dbc09bb6a352420f09942e4005c669c5b5d8b406c05937e5a05c6b30016ebccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63099
the chainentry 63099
- sealed to the entry before
- daec4c8c375a62590376b593aa02631c068706971c369f60cd38568ffeb46e6d
- this leaf
- 02234ac216f9bb5e9b8c21919030e4e1c7b785bc32fd4db92af14f8faec2ef2b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RrGjiZi3vYiAWz+qhpRma6c7At78nZh2BU4sPQUz0BeX2q/uJoZ/hJPSm2ES5iKDgVr003bnjBeWPs/vd7lWAA==