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
- c12e4c8c5d40cb4665d98b4f9850fbc0965691d5dd8dc84607d7742440dc97f2
- request
- f77f5e14ba976a291f625abe4183a95280dc4489b7484344a95519b374a3b356
- transaction
- 53e55db3b56759bae652394196e9a3da0825a0af2c97313184f7cd4ca3653e65computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37474
the chainentry 37474
- sealed to the entry before
- 052a1804dd0f8a71a976ace8f6df44523383c179df5e894363b7dabad663ecf4
- this leaf
- eb5aaadbad39aa3d3ba38d3ea2234f533e0e59a0eec0d073cde81486ec01e789
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GkFs243qW3e/sUAu5HDhXc3rnEBaZA0Fa7hg2GQROKbXuND9cGsR8hjgc84AZ7tW4ladSMh6/Lbp23XYCE0tBQ==