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
- 00385ab148e3671b724b37e6c1e61fbf8bc664439ca64405f4b56ff5e63065c5
- request
- 59b09f1a2dd127f2b28a78956511c3782937b6cf729a9743b49bb753b4ce33d3
- transaction
- 36ef0f04fa86439567b10925c588216a7dd68753661802a7a2d10e5c5ac6678ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32578
the chainentry 32578
- sealed to the entry before
- 9da8d628d2f525d6e33124793caec1a6c8de457929c83bfed9e8e01a436caaa5
- this leaf
- 5448c430d7433fd4ab4d44523e2acfde26be981b3e859d68cd9861782649fe1f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aWyTQa087YO2VzZ3Yj6lJsby7v0vgdzhGfvfT5NXpTq6qm7qS7OTlRxh8M8g1Kki0odtRm5pLP7I8zw1Da1rDg==