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
- 0429b17af676417db04f1f2759bfc8cc62f2bb72ded91263b3f5768a77756eed
- request
- d8ada97a5c9286ed32107d419aea81bba0fe75591d0704955093817e5883501f
- transaction
- f7ed83ba38bcbd9519419925c969077a3cf400986b1181b391cde37f29a89691computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62960
the chainentry 62960
- sealed to the entry before
- 9959e90cdc3dbfe03fb2f6668d56d4520ed5f06b71e246191d0bf549dbafa8a2
- this leaf
- 029b52282e850cb724db2a4efa4d6168aa590447b387ad3627c376046896f5f3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BpUfor8YWwYxyKoWi8anXcjBVj6hvLdhMNDeBPBSYpfBbsYkev9+rZ0GGESosg6LQvwKhz4Xr6pO0iiW7QMJAA==