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
- c82fa33524729ec6b35c66b9df5001c8ed4b3208be21d5455ecae2e9e4955c6d
- request
- 47c5ebec7b096108b1df83d141b233eac43a694c26a0550084a94f131cb56fde
- transaction
- 1d7979c2fcd3f126459f816de0400172699a8129abb5aaabb7f202d6cf8a16aecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67069
the chainentry 67069
- sealed to the entry before
- 4d25b19914f7fa21ba4c27c7c1edb2486a6bce89a9fa6e7c97e31c9795b01c97
- this leaf
- cb9537246472f7a349b7f2d2d5c6326882ae9302899846fb9b49a3fb3867fd81
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bVBPmytry3lMda5NIv05APW2vWkwKrs49/GkNI6L5b0e9QXHHCskuPLxBv+rjoskwdLCT2jZHDzmJDkYSKAYBA==