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
- 64045ee19bfa001973b00c9d3499e5349734974f34fdc10302216dd4b84a6e8c
- request
- 5eae2fde28b988861f3336a0e2c8fa3054cc796e99e0e9470e57f64074240edd
- transaction
- 2a050d44b7a1548e6d5730d96615dc7cd81ad7b1c66ac2fcae368cec519a70c0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66933
the chainentry 66933
- sealed to the entry before
- 69074258c721a2b17797b465f06c8361d20d64cb439e823c10f6c6a8c051b3fd
- this leaf
- 81be11fbab6399dcf3732b42aae2252d8f7935533775e30a14fe7c51f4b58d05
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bW3pYgUngHvO0+vnroMqgL7+ttAfBjqkRlX47YDVfG9iknJVjcy8/N3KWBVRKlT3jXl4bAscNItbuxQe3SSqBQ==