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
- 49b0563c0de7cbabdc9665efb5c7d4ec8a71a5ce9ef7377162a68795f7dc5df6
- request
- 5e36a7bb65afe75284be4fad7be9b3e5ae113d8bb206a30dcc4da2640d212389
- transaction
- 104ff9fb474b037aab31bf41b219ee45ab97dc54fe9c531e67146292b1d03171computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53466
the chainentry 53466
- sealed to the entry before
- 447a5cd3f11017c6902bc7b2bd13cb9c51e80a45b28b2dab7824605892f5872d
- this leaf
- b08ef3445c536bb5b6bcb770d43ad37dc67adf33995c725acd4bfffa1bc8b20d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tshPnrUamaj85ucUJXhNv17FvUtulL8BpPT6nbYM9/O16Hy4KnwqEQb3P8zu5pw3ccQneVg1Pwdp0r8pxTTiAQ==