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
- ab0ae0beff3dd5827dd6c130e1bbcecc0942069de89ab5eb1407203e3921e662
- request
- f6435894c059e21092805914c7ba5c0f70ee033940a06c3e8f28a76bb25cd998
- transaction
- 05a38ad8f1ce68d3861bc4a97e50fe2e50d597a6044185ef713b7beb2c6fdc0fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22099
the chainentry 22099
- sealed to the entry before
- 5618f6ded101a904f9fc34a50b6eca92563927a432dc60c3a0acb3f0b8402165
- this leaf
- 6253e0f82170ebd72eda3eccb45e116b7220ceabd3dd0dffd259d5a97412677b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kVNPVuJsBdCDVlRWP20tZAM0HbOZPnA6pUrFk/PVoA140aCrm/P/+Ysheif62jzQwGAAQYZ3b7tPoWsLlLqEBA==