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
- 1bc77960d4b58eba9834985b66f9b72b11ebe9f508cf1cdd9490404bbe923e43
- request
- 86bef92f80ecea40f12fc57fabfd4496469b46487d39e1b0a568b2748f7b13ac
- transaction
- 18d133388163b8869a9bd7d5fc0fce4b0ab4f161fcdfc2c0719055ffe21560c8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1605
the chainentry 1605
- sealed to the entry before
- ac0db2a073583227ff8481f2abd730ab4c8f0bfeec38f6e51c0550b1b827c9e1
- this leaf
- c4a8951189a576e3606542b6f2819a47fdea8d963697500bb0380a5fe4d5c929
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MWDTbkgO+83ICpEIbiOxfdMAUzJiktQXLnh+toaCAXpR2wJszkpIBkHxWIAbnz02L4vkZ96/JH6GgIF9bI/vBw==