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
- 6906a331e92305f3c3a4e9ecb343116547175d91d66269fdee6dd4b58fca94ff
- request
- 2e520475e9ba23d805c6272f75c8dbe31ae563b2b43cdb89170499a8a30bba88
- transaction
- f95a418f83175b0bbaf4cb03a1b64eb4cf2837e1e89b5f63eb95b39d04d1ec39computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71802
the chainentry 71802
- sealed to the entry before
- 5acdb3a73ce9278d1cfc96b9a97a9dc86e6fdc06c38fed3995457e3ae55f68f3
- this leaf
- 5ceb260eef831166271a2b87e8f9eb202c7ccfa34962f62003f5152539f5cb16
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D5jAWkB/RYHLScbO9G9BDj1qOCpLhInUewW7ZCUEN40oHK6KDsAb4woVIhu7cVUiSCvRIxHoMpgKY8ISy2lbAg==