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
- 836c09ea5b54484e345f6b7e989e2f4451e1a569ff16921e9fdd7e534690181b
- request
- 873a7ce139ead7d4dfd56de8248bb69f49f62851c586139ecc9628372af4277e
- transaction
- 120005cf1a479206f2e2712abd2332ab095f200d17958776c18514cd7952777ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43148
the chainentry 43148
- sealed to the entry before
- 7e5b1dc5cb974d7fbe70c5fff3cc2caf098875638cb7c8ff3d924d9bae2e028b
- this leaf
- d5eeb55dae0fe744a748bc0040c90f08fb5494239aeb3bc0d93530526c9fb7c5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Xw7aG3Fph9oWaE8Oy4oRAxx0S4Jm/mNaU6OYk2lC/t3uIUw47zBdIhZT1OFEy/K4hVD5WaPOQZ1lx7xR5vHBCg==