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
- d723622a9ab623f38d754ae4a52badd40e6eafd5ec74eaaa0ad18ac626528c7a
- request
- 471c1a7bf8d571e9d135c8f58d35dfde62a57c78c33b9750f56bad027e9eadf3
- transaction
- cb20fe82c1b83a6be9dbedcfd03667f937f2c57507bb92b750c76ac44ea92d84computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72505
the chainentry 72505
- sealed to the entry before
- 929e06bc589931952e1a96fd22d3599f0ac8b428c19ce63fcdd9502bbbd206be
- this leaf
- 7d5355b51fa1af65d60df2da02c7f3180ebdef984e9fa92ca7fca865328a11a6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cSPsJeipUscX6V1oSZeTprrH1aD+tNgJ+KV/9lZfE/4161ZmJAS5I3S10k5WFW/S3PCnYN5p9rtQwmCxr5VoCA==