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
- 4f4e094caa5422b748931b49fecc806ae346d44b6331775b03234cb87cb9d52c
- request
- 5fe968dd8e4edaf056926516029b9a8f61cfabfc5422a06a8b42e416917beed2
- transaction
- 01f695f160e7c19beffc877704c5c63683f6f5e80f6f353b81d1ff555726803bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27305
the chainentry 27305
- sealed to the entry before
- 076ceb807aa995ef4b6faf64cbfb0d4937657160c816420a79b09d501219cd5d
- this leaf
- b5d66c820d67a1bbe44bd7675d9d06d98bf4b91fec868a849e38444c36cf0191
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VldwI3z92l2rAB93miocQmXKdCh6YCfeY0neiLuNMmb5lzMcLUNSWP7ScnQiUetFDQ4wYwFfa7TVuHqbRS+/AA==