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
- cbe1cbfdbce17eb53a30bca4647b93cf4be1e0e89a21a745bc5c5e45c693eef8
- request
- 2d5352f8df08d2501e20f84fab77d2472df7aea6aa60a0788edf50e14ffab864
- transaction
- 8fa96e20f2be7e710bbac0d40bffacbfc09d6c40dce185c3b2e3c5b72f41f5bbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36040
the chainentry 36040
- sealed to the entry before
- adf31f13dc4b903c6dc7af2d1c3fe108a05bd4f5c0fef30bc03c1ba18453d10b
- this leaf
- d72ef0888f0c921396812ec0d7de67840a4b0b67f133745890c225e983217a0a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fYRBBpMa9OJ7SDf0XlGHYE/OphdWteT6NNeXycmEq3pOJo5eESmf4yXWasaTqsjyGo6Az4m3tiSs+v19H29HDQ==