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
- d3cf4c280e7cca2f26ccf2940fa0a589b5a86cd49d58779cfbf70916addf81d0
- request
- eaa61313b7b032b2c0e88c2eb374726de608ccceef1193bca99a3b2ea7cea55d
- transaction
- f81cfe6d4427deb1be5e006044a592dd7761cc4ca20c953029002d41d4c3e618computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62415
the chainentry 62415
- sealed to the entry before
- 9402181123e9a042f93ee891afd966b113583b18f274e2d9a221a6b4da11b940
- this leaf
- c9d9cdde659f556e174441c64853ce00ae9444b36cedc5b656d5b8ceb5b2ce02
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xnFVGFV0T6rhsY0OMuc9DAx8ylU86Hs3oMv5z3IbQMPOYKMxfwTrEEPkSmIYHeNnOIz3+W6DQeQq/eMwnsx5Ag==