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
- c1e4c4c769dda51d3bcb08495bbe4b34f79e1c008935ae165a48ad92ae7a9189
- request
- d7268a79dff98d9484de77f7648a7374fb29ddda4d8a020822080a814823f7d5
- transaction
- 9742e659c80861b63806f9817fd69d7b1e4605c89e61881b1687995e300c7950computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55617
the chainentry 55617
- sealed to the entry before
- a83f010bc1cf55a35015ee6eec0d66a027d32a1719fad728daa20da36a8ab50b
- this leaf
- 6ab484686511e92cf86c892c298f804a66bb34922f6e632237e156e6b59db440
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D63UDJU1Vk2Bt7WJgyoGBtUctDP5BAE6hUSYCUaSyT4WsNh5JjxD9eFsAF0sSboly4NWhEgLFoPLxF+K1m/aDw==