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
- bdc0d57ea40962f227078f7406186ebf1f856a3b1397e3e7bb9bf0368131bde5
- request
- 3db7c0d31179608f1183e781ee3b46ca0c0da3f97b99a0e4f3da1386516fd4ec
- transaction
- a95b153617239d3d567527c256de16e7aba4499a0b3ae56fc72411412d906738computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63694
the chainentry 63694
- sealed to the entry before
- 341b47179d551e35f08c6868da61668abeec7d2a8712f489493cb14a8cbe97c1
- this leaf
- 85ddeb3a57a28dcbbf52e523738efd495da0a9bd8b825bbae3b5680700cbfe75
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TV2Y+GJnW5ethyyUI+HfSTYYDhEPCQ9pXSuFHxozioyScoOmjrnxyUauGT+sm9BZB+C05huqnvDRjmlMSBWfAw==