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
- 5370bce7376b75740a51ed0581fe613a8d42a0e9ee6665cdbf62acebf9b0a00f
- request
- 7cdf11faf08796eef66bf90db6c6e34f2285eee744b5f95fed93874a2a887340
- transaction
- 293481c894976485eb0f8cbbd3b3186030499d3a06ce227f6561a2d8cf5201c9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43346
the chainentry 43346
- sealed to the entry before
- f9d9497d750efd40ce1ddf1e5f7d3d5f6c354f5df7a2d7e62fa73a1b8667e315
- this leaf
- 2a04797110ee2b50ba585314ee20802894006366fb9cf3bba1e20cd520cc97c4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dl1LxnJjqwMdGEYJ0EO8XoqZwd6pCb2jn4gPhVAwrjR4aVaXhSCxROZThVSBxZWS966WBh20hbn3GMiyrkA6BA==