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
- 2df524f5dd08ff3ffc0188dc6a4ce9a49baf907b2b0fc3f70e7599fed6efd5d6
- request
- a40b4af403f559c5ac5fa245732b25772ede2533a249d3f6438adcb3dd7638c5
- transaction
- 04463dd29947767333921f38ce73dc1940fd8b361cb6b04bf31274f3d4a7eb81computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48614
the chainentry 48614
- sealed to the entry before
- d7a57aee9d68c2b1ede7dd380a4dcd6586ea0939f987d5a08bb26ea08353966f
- this leaf
- f508e53c335646a7bfc103b7a3e40a68be11cb36b8f24c239549bf82ed4d9da7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vM90+cDGzoMdO/7OlK4VRhs29aqu3x94D/Z4oYLys9fIeNMXlY+NPPutNlZrOwbLybgn7BpldJMdYkzKrHubAA==