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
- 6b859fae42db0ca3027dc75a36f4ae5a93abde01a9c4bcdcba6ad35a03a55732
- request
- 5e6c3531dbb42aa918b783f1f3b650e7922edbe87ef8da49ebe01fc7911f4167
- transaction
- 81675ee16190a39d96373f24f58aecb6d1480cf2433e50dfddfd18e5edf03dd0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17037
the chainentry 17037
- sealed to the entry before
- 0376e9ce266eadd67408273a03d480094b342f535f3ae4bc75f6e21ce9a65c52
- this leaf
- a1733440e8dd1f458e56a000f8b926f7384cc6515ff1729fc9fb480af6d3b0c9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SvSaGr3qbAUvOMeSpweTeGBebYLancehrUqaQ/7vqyrSw7ppxN7XiM8yBanyhetHigCBRs2RM6zBiwRB0aXiBg==