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
- db282f67c7ee04ff7db0062c5f4947bdbdf1221c8951c5f7320aec14cb5f4155
- request
- 70b18b40fcbd9021027165b8d45dc677f3ca20eb7b1bea936e7605e9a680ec71
- transaction
- 1b5819470eee512841e7eebf922b9434453b90f19c66601dc1f432feebcbe125computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42170
the chainentry 42170
- sealed to the entry before
- 53f80e2534991d828a7c3c1970618a9ab01723e3d6190acd827145133d3fbada
- this leaf
- 144075470f4db54f7b4dfff4f312315cb26de4d7aafa930f07b1912dc12fb388
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JNCqBLgG30BrasToAaw03vfkELzTv9u8yC9X7SCuxcIK4viXuLauuA0DTpQQZ0IweW49loF50DnQlvuwGWupBA==