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
- 5e05bc05a8a644dc5cfc386f589b7f2412e2af8f7a910adcd80ff68115eac841
- request
- 9242e1301abb62639df77f4aea404e407efe5392e0c6b7bd6bf16a96314dc448
- transaction
- ebfe077523ee0775e7982ea12f33254af91857da9871dc5c10c9f3e78a993a92computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31457
the chainentry 31457
- sealed to the entry before
- 3f634957a730b0262f7e305ff96b54fabf25629ea7af1d10b59078c6e8cf5b9f
- this leaf
- 132b957401fbba41d3085ba30aaf95b65d616ad3b06c62efb09c1f8648e3d24d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xgcXlar0EYmtgKJD4MrCb/q8UxinClAbs+izzN74khAiXRpqIvpVFvvRH4F/l0BFWhbTEuqdxQIXmW1E0G1IBA==