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
- 473b56d3f4f481bd1a26c6cd57cc285d558af86e7bda005bad4cb1223d4ec542
- request
- 5967520e1bf4330649b7ed73f6c460621dffce1cebb60e5fa6c51e2cc3430015
- transaction
- d8966dac2440119b1253da8f97aa0b5e139d5a5bec8be73c3f3309c03a0176fecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50926
the chainentry 50926
- sealed to the entry before
- 308b10ae14cae2c139bf3403f63a85cceed41ad9673243ad34c5cbe971402a8d
- this leaf
- 70cc3520146a2816eed038036d5d86c628c5da0c454c8f0fcca20b27701d64c3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mtj/zac5U9H2GPuj6u/QXb6oVFGn1TKivC5o7Vc2oQHhPeDOODjsCxtRzQYhubJgTVnF4MZfqdfGf3oKoMgMCw==