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
- e025da6eb716671c6191b72cfde109ab3d967f62902af4975e636a1a18516e36
- request
- 444519d0a9459dfa93439f51ee5e41265a853e50557950d444a3f9c020e8204e
- transaction
- 2da26ddfb91d05d27db96a9a782599e123dfc69c43a71a98a455a6c6a05e090fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1048
the chainentry 1048
- sealed to the entry before
- 20d93aba5963039d0e170afc8a1c755350b382558c2f94bf77e81d1f691f0913
- this leaf
- daae8aee49bbed81cacaae46bf70fd7e5fab326d29bffb0fc82aeb8b874e745a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yhbT4ytQeQZdrsJ3niel1LvJUlYgEAB6v6N9GCViqxjecV/YIJpADC7XEZMQrYesqVEmCvyLWRPgoNVAXpOEDA==