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
- c855fe91b51d5ee71240766791e2b807c2840fe78c785a182b32018dc9541511
- request
- 4919b08c675150bfea7f65d5012294beaee29f868edb72480afebb72d0f5147d
- transaction
- 1ec7a0a967ed34de9e504d3fc39da6a832c13507317a7524cd4329a10822b451computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40179
the chainentry 40179
- sealed to the entry before
- f4ab80829d6c2708763d0a9f6ea11fc5e8eb8951775023b41c0dd3a5edc69193
- this leaf
- ff1e1b288259e6632f527ef44883f5a13a4eb55e4ec345a4369c2c0109776261
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TaAPpCNqndSMLSVgw+bxeuctADyXwsP8tgWcRvmSF6K+zKxQ5ijyK3zF8JLkeuPcQyiwSBtdNBuwuR7wj+MUAA==