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
- c0d88f315d288b55cd078fcd9e5ca6ba7f8f4640cdaa885141f6ae327792c088
- request
- 075ff94e64bdf7524257040cf947ba452677341766972874a9ea01d9ad3471bf
- transaction
- 2467733af32a06b52e20422968d6cbada1fab32caf8bc108abba594dbad0f304computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74752
the chainentry 74752
- sealed to the entry before
- 24b0f4c27d86815b8818a09230dfd5e0e381698d86fc55a6e8fd67c759ead615
- this leaf
- 049e0285e09adcae1f49dcd6642210f8ab27604a2f4d1663be9bfae2926954a5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6dYFIaV6pXu5tlIOHr2yPn6YijjrnoJc7n+UHlwDHqMtVOxkgb2MMPq6E/QyHOpQFZtDQ7x4/Iy5W+atnnx2AQ==