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
- aaa35552e5188c732fc1bbc1db46782ab2ac26685215c6288ef2da3e1fd19928
- request
- 9d275a2f6b10ca53ef2429afacd34cc5ba1876ce1bdf93ab8e22bc23265f1208
- transaction
- e4cbf551bb1a0ed2a4e3444d07fd31eac7591150e24e9bc3e22acfbe205babf7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45390
the chainentry 45390
- sealed to the entry before
- 430bec63a5204ba38a03ed9149d4daf9a82dc36e8db34f8367f1dcd6352e2b4f
- this leaf
- caec2f09bc0180c4bc1e8a151181ce0b096ed0e409bb8eef3c6f3ef6a28106d7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jmzdygd/rkjCK1dU/anJ2v5x5oLO0iXxn/wPybvpRX21p3MIwoBAVdF/yju1HtSq5KNIkUzCmCwPsULerw2IAw==