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
- a043e2f158fdb8bfcaeb2b1f6de8c833c1b794ec55228d323e793b5d60e70000
- request
- 901468436cfb57017e2938872847c6fb11fa760f9df0a4f1b491ff03642a9952
- transaction
- 3ef09ddf34adf3d660a4c3c95f8ba3dd323ff5cc383887b59a19405da086ca04computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44674
the chainentry 44674
- sealed to the entry before
- def33375aa8a807e3bf3e2ccce98668ab693a6e625f8a91a4d1295580c093bed
- this leaf
- cd4ec895575f200ad04b52ce2ea8ad58096baf9d0750f98ca66c3b8d4cb7679e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jxNLuZ8XKBKl44oQGyJu+IYJ1cFGapV2Z8OVlkWGnUjzpO0/mWHNhSWD2vsiNUtYF1qcaVvL6jQ7zhAiiNPbBA==