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
- 8e0b79332bc198279dd49dff39c93f12fe0b1dd642ead7079c462ab628431fa6
- request
- eafd0e0a7652515712628a8867ad642caf0d4f4453a78eb064222059b8f7b72d
- transaction
- 6ff3d7b0aec05c1035b9d5f8755d2b6eaac45be1a43108f07dfac33be18f9362computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42962
the chainentry 42962
- sealed to the entry before
- 1fcc8fcf5b7787bfa4a9d8a7b6ee0fac7ccae5c59b72c11f674832985ed82e39
- this leaf
- b3f8fee3df2ed9c72e9e76b5ad5de6b2f223454d582786afdee59ddc16176688
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vho6LFNmWTyeBGPyJRdyVvjdTis6iXZKkYcVgnuP77qUZb05q4LjGMzuR0nvjvyiA4/xsIDLfBESXQvz0CYVCQ==