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
- 90ec701a0867898c870ed9f767f7c6e47778039aef78d9840c35531d45d478ef
- request
- f738d9e9f62bada1cc80ab00bc73db45f8b465b8c8c259d3aced3b465f8619fb
- transaction
- 85fb7f83266bcd5306ed71c21eba0eea011c88a1535efe1d1398898f1d1764a7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74149
the chainentry 74149
- sealed to the entry before
- f2a29cf90f8b110db4aea1a979070a330bcdab28b60a48b17337c179f9b865cd
- this leaf
- 08daa12e6e8b6257982e74435662bac96ea9ad43ba8be2355188a08cc1e79788
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9k90XDvSo+7CqZLkE1pB3Xfas6IXePnIkshGOUuI68qU6FIU+l7rIRuYEH0amPgbrzw3/PyIc4NtJshTjcjDDA==