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
- f768a0038a2c253de16931120a6ebc8862147003f8abc62827d3849c0649bfd7
- request
- 2291e2709887165632db90ca1d550d7173f331f76ed33ea8dd3edfc1597b964c
- transaction
- 2ddf0e9cd3b8b4c85f32d9ba11e8e5d5d291a02989e1f88ff88f66adca863cdacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5266
the chainentry 5266
- sealed to the entry before
- aec8e104ff246656e90aa3125f0df7e10f77056bebc08cd0c61e162c6d6a877d
- this leaf
- 0590e89b00d5fddfa1ae03de8239137b58b4a573cca7d3d87efeee8be8ac8fd4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZmhVMVKzlSw5QIGU6nuKijCZPuXEyU4IcuoGk3Y5GzhUglKMq4KLPeYSGCOWxkwJhsn8mdDaOz7MIGkR13SBAQ==