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
- 9826a8f7f52208178615ed1226fa915554f16a7dc4d62578d27ff3264cf33dfb
- request
- cda9c95e82cb585c61a3fa3118a47cef153fa5c009abc288b20f1fab0378ec08
- transaction
- f9570609e31aaba7b76161f210c6c06d03e14ed49b6d31913ffbd16cdfe940aacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55996
the chainentry 55996
- sealed to the entry before
- 529bf596f677b977cdf1792c58979843cf5b5e873a5f4fa4af5b53e576e55b7d
- this leaf
- 4b8706e365e0d260c8b5a65c656a0d36f0d0be0082826a3c6a48dc15d634f409
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dr7t7uMTsGcbp2smuT28KuFz1CfCOXMmZwKIHQGu7PoQpF4N3BtYq5E1YkxWh5dhAxZQ2EDZ6jwlTKAQj196Bw==