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
- b39e30ae6fd29ab27b7bbd103588b1d96d8999e1510cec8dbb5acad805508d23
- request
- 1dc14840508a4171600df3a1a19ce1d83d8dcb6ecd514fad53cdabee2cf0cdc1
- transaction
- 15c617adac2e6814e62066ff5ca5fc88d1160072acfb101abe8d7c07bb9c1194computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34716
the chainentry 34716
- sealed to the entry before
- fa1bf44823ec4b3848a337a84ea9d7dcb12e1fc784e061d92881e33b2a47f233
- this leaf
- 5f4bb024982c098918b0d0ac24ba27916bf73eaa8b4e024a4d821aa26050fa41
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Z3YTUqzGXX+Ia6E9TggCK7UahvnJ2vtDhfUJr0aslbmti6DBneXbP0AhI0mVHz0B5Aa1NuNBOf8s+7+VowI5Dg==