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
- d2c8455a816419d3551c72d188e600c7965445e787ab99690758a7cec26f32c5
- request
- ec5824b0bf67e329a483033de4e72a2eb89e979359949d277a5b21ce1f32a013
- transaction
- 1a6b43351b49a6be542e3cab88cae1abb66899e3ec0cbb1f686549d90a55c5a1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1880
the chainentry 1880
- sealed to the entry before
- d32020b163ac5ea00415f61cb689ff5f8ca5b8646bd0dcdee00881453834accf
- this leaf
- 74e40579fbf700001fd5962871ad1d7d5e27a0123ba0a9de0ad80fbc7a7a6b49
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XG5NSAzO5WgZgva2EPHgrsb/NT0HEsfY/xlV1uR33F+sSX4ky7250CSIz3GtF/7NQwVd7gfWnqOg7ohxMMg8BA==