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
- b682d758591bd05d6ddc3fff69964354c56a5aaa62efaa5ba0916e6a8905ac1e
- request
- 94220c28dd962f49b98bb3fa8a74e1c83c45cbe35eb8b578f870e3d3f2c36141
- transaction
- 88a64116d7d050bac925e9d43afb8c7f915e29edaab1239e650c7c3ab082a19acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57242
the chainentry 57242
- sealed to the entry before
- b696b0c70b007d3c707bcc0944343ecaeefe74a1e29e1f68cba6e2818e6be7e2
- this leaf
- a2afd7d331eb3c7a5a48adedb5fcc898123e0392bfcbca9bf8a7f75c35582042
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5y9+Dc42m3gIva4R8dG9Z0270j+thxG8HR8vNGu7A30TZpI4Q5HFio6pk0d5eUCzGnTdQDRrANdDNnzfO5HMBA==