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
- b15fee2b1070c16cf8ae8c9dcae472fe1218452f9136a129d3e642e48095dfda
- request
- 0d8fd1f7a3e6f856deae63b9310316fc63afbfacd1561c9592d4988525e33f95
- transaction
- c8e290e4216371c5af500b663f482c727308b16595ca76a9947088cd2a541cedcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37480
the chainentry 37480
- sealed to the entry before
- 0f0dd50dd0087fd91e005ab710abb6b24aaa5bdeec80db8c9787487f021891ea
- this leaf
- adfc274cebddeda82e1e4c80b3640da2ac8daa541062b9c97d82d9b0a5ff20cb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5tfOXCzs9qFmqDzuT3zeUU9EmIYL9b+EEhxquaaU4rts/XMrHSvNYY/glPfv7TgOW4HatyX6PfaBJXbD4ov0BA==