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
- fd91cc6d6e652b861b9865061961e6e89443ada392e4035482afc49fd14483c6
- request
- 298bab023e96eae6cee0db72a8767e4e95a31a3b3dcc13e9478b251433e0ca94
- transaction
- 29a69f48e7a7fa315c9cae37ddcbe5625a761bd3e48768d6625860440bfce268computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11190
the chainentry 11190
- sealed to the entry before
- 4447e9b356ad481d5b30dcc141387766ed03ffed9e9c93f7ab77044e7cf6785a
- this leaf
- 3c003db3198c80e28276c15df7d3d8ed6458cce3bb384f56b9e03db06a5cbfdb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 23HGMPYUsKPR7kjxmi79rTm7xvSYGwIllpVOmeRne/KvfG5x48fLTF/Rw63pA71b263UJxVq01ebGtCVCgRhBQ==