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
- 6e349a5f0fc3e714e8b0bdf71fc1922f61abded2c29a131fcfba70ff46d22b3a
- request
- 97953d80c8df9c7fa6991f357fcb97e88af20d32b36ca42aa0fddf740407c6e7
- transaction
- e4d3ef40191076ae2fc6b95171e6a6fcc54d5ae170845a4d0e8a4890a4d9c356computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28619
the chainentry 28619
- sealed to the entry before
- 0b6e30b4d95d550aefb7cefc8881573765d353cff26356e87d6800223b71d59d
- this leaf
- 887f4092829b39bd890ef617ae985b64af84d814dabb43ea0aa306ab28e16ad2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0AiubzTSIXA/fTudb8ujvPULd/WGGJ1ViyEh4sQsqVou8Pp3Zu9kwcGWw7sVihmlSHZooUGJSiOVCTtxo3xRDA==