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
- 85d2c310dfcffce655b5791b8601fc1ff2d3ced53ac888773afed680a5b88d3b
- request
- 89a26fa8f9b611db4cf376547aa15c7df160ee5ef1de3b519e5698877a22d54d
- transaction
- eb01a043eb04f4b75780b4bd165f2b0274343ef17870a0609d9bfaef5ec3483fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44728
the chainentry 44728
- sealed to the entry before
- c4f452e8bbec4700f6ba6e9644b6a57b06d1f244f14fe9c482826720dcb562f7
- this leaf
- 86d4554dbebea7202c693a2fb62ae2693cd08aac911bc4ef41fcbba3d1cd192e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PeSQyQ8jRhVGORGeHxOByVQos86HKeuYWjYOBV1rTZWNVFPGA0prNJno8BscGJtcW3NP1abA3a14Dj31P3VPBQ==