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
- 4a72e80cbc6b12ccea2eae8db59125724a3eb51ade4107cc6f02d652cae4ba34
- request
- 66fb8b3476327669282fafe302a4f8c2de0d71d9ee2db1dffdd5e3842e796ea9
- transaction
- f6c169ff64141c0e2777b5449cefa2464029dd2dfeda86b13db1e2a3cfaa0416computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73689
the chainentry 73689
- sealed to the entry before
- 7aab81e133d97efd88a16af34eedebedb3797dd68748a6426d6e5f921d868f52
- this leaf
- 4c32e69693a16d104aed4016e26478e784f352e5329ca8fe05fc797b7e6a6631
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- K7n/wUEADoEyRDnfTxQpMFXXLxfiHlD9ZtsNcqsDyiI9JsZtpLDOaWEsV9wb8lEcKXbXJmTVlt0YD88rdMiNAQ==