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
- 7953e4567f11e082735c90c14e15e98f470a2b774767092b0354d2e594f9414a
- request
- 8c7860c3d3044992fddc53f55174a960b72b4176672071e778dfc1e612a34281
- transaction
- d548fbb46bee6458fd60ba48bf1b4163985959064f77f4f1ffc9db4a3648b6e3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54190
the chainentry 54190
- sealed to the entry before
- e444d519d9e59304a00ad186f8f667f83c6043e6c5251cc636fb1f50a705c466
- this leaf
- 3e3e6f1c1ec8360f2e69f640836b3e4cf84aa91f70b53828400932ae99e62ddd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5Gc0J6F3T+kSkXDz0+BtNc0+Cu6WzKjFlSFmdoEmF9EWvn/NtFtAFtZFbiC7/Vm3FQlY/Xay2Rafk3Xr+iKDCg==