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
- 4b0016f4ed0904131160963db2659fe23be52025b0b78e336365d03113f90fc7
- request
- bc0c23a301536e12c82ae141e7ea9b58af0bcfdafadff8379953ca900ad8a9a2
- transaction
- b0632befd4aaa512bd5582a9f6441da1b3fd8e79e7574370cc3d0bede2fa84ddcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4142
the chainentry 4142
- sealed to the entry before
- bb31996b5c7b4be1b755261bed072b7d5ee375ece89e3575e0e0624dcd78f358
- this leaf
- 93e11926565375dbe8bda60005db688f80e59b3717054c33065f70bef4cd1c02
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rezxCrhWPZBNlwFE4iU7uxWz7kLLKoOUrlM9MJs9klCyaC0K4KHXGdbgqR9Kce0c/It68/2Xxr6VeQwqgggsDg==