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
- 25c67d63a98fde37ddb4fc9429a71572ad994e8df1427e15c13589e12bebd056
- request
- 3e8317ecf86c42ffb6b2570449f2fe8a1c6a38edff34fa850d61a4d7bbe0c726
- transaction
- cdfa0e7c7d8dc5fdf148d2f6e66b03f709643bc6e8617b31c1e69820456467afcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66328
the chainentry 66328
- sealed to the entry before
- c7956d0a67f890056de0dd7d794f0b6286b4396945210383086ba75b6eb917aa
- this leaf
- 896405a151874d95dd9f52999055237fb0c026d57f79d88d59d3f5ae162ba613
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dW0DPEp8Hg9ARRT62etoI5oIt67PiG+/dpvexanVEK90yPAbJOFGxdOHEoqk1REiK4akMlwUTuYgHyto068SBQ==