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
- b0a20ea1f498adafce50ac88a13f814a2a473fef73724bf1b557a542a2647a19
- request
- 09f6438998959745d59e353c49be097240a50b5870f378f958572d8d93263e8f
- transaction
- 5825816a18b835acd855f8a5ba9d35bbad36019974a2726611253075c5c0c4c2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1435
the chainentry 1435
- sealed to the entry before
- ba78dca43e875c0164a313a844ccb2986b1fd614047c4f290be59a1f658b2dfd
- this leaf
- 700e4a904a3d5d66bfc683f226ba59491814348c782133249de20e1baf82f8d1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8XIvyY2FBE44gOtI5jz8qwzu06LgQX+GemOPbz+v33DsYXI3sFnipYAs4ZTZkAm8yMFpyBD4lATRXa4sm3a/BA==