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
- cd82b86d31bafd6d9c3ee7067ced17f6bb03ceef076aea3003a57bb0b4fd2656
- request
- e609cb4355e77f48948a57d4358ac07fe416a16ca329d0a8963164d5e505c6cc
- transaction
- 95b74bbfaab93d2c4594ac1aec912e54de9bca43de6b0eb22ad215d434699b64computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61
the chainentry 61
- sealed to the entry before
- 3e50d9239b13941688c58f4dd24641abd2573ae597d86fa80c8f0298804297e2
- this leaf
- e55e1e0aa2a1b9a42bfe454d9981a592fbb26d13b62981da985f2410c4a883d3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Olk8dcnlF6FYHLRvLSCuWLIfpWU3oBUEPGOt5x2Xg3/vY/WjsaDie48939P5b1p+AEp7Ijh2QRJSorxvKzncCA==