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
- 066f42b53713c76c62fa1791378945f9e447acb87e0f557392fcf09c56bf7bdb
- request
- 4c9b0ab6bf9465a26726726d484cadef53c3461b73c33b0cf0b19e450bb28712
- transaction
- b826b5a665ae251399eb0019dc74db8c5592a58be08c0b951dbee1c296497463computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52913
the chainentry 52913
- sealed to the entry before
- c6f7db052edfbc5582a2eebb6160c37868bf98e6f3ce33dc38cb7f1ea2bcee6b
- this leaf
- 7338950ff59696faefd7182732a2071aa4d99a9bf6359ba0dc83b3e7e4b737d1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vWg7ZYVcW28G49baftEsyUY9Z5/G+Zx6po2Y/wj/Hyg6Vg2OBgo1QpecOW9zp39/5Q+zN6BJ9aQF9XFkgcXuBA==