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
- 92cd2fbf331d1e724a01322dbeca51ae7ed14d7361c47d5570ce27339fa2b852
- request
- a7945831a2528fa25c7492090625ef849f3c08f68e31191fc0225c8ef1cb0695
- transaction
- e9ed3ec3ea92f4389fa465030a6909b67063dcfe38478c6010d07b627a96ddaacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40100
the chainentry 40100
- sealed to the entry before
- adb8fa17fc4ac0b7322f1cce1ff12b630a93a141ef04e89aa320abfb66d488d3
- this leaf
- 85d69635c6dce23e2b6107795a43e6bae9aa9c6ceabf9a2d02dd82002db7fee2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8VZZS3ipOqijX/7HWjtYV5z2FSD4kSU9DXaNZflVXyaiE/Mqrrcm/uA4N3X1RUld7TlSW5BAYn7vHZVVFR4+BQ==