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
- cca40b93f203f792cfd20f485c12a00725d301120a89a1ec28f6c11e6ac86041
- request
- 837d1696097f6f2d1eaa6c6c173da57106acfa11bbddc1b7a57a869e3a2da755
- transaction
- 44c89d1f6c7b80bea6ce82c4bac745184af96abc15faaa570142123be98d026ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65128
the chainentry 65128
- sealed to the entry before
- 432b0886195f0db49f1a7e7ee595e9d62634bd87093657f222510f3e2d48bd53
- this leaf
- bef61a4e5f5de18dc3f74b0d985b21456142c2d2f7a662721d98c0d388a0f6a0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tLnydQ8ecmmqdz+t8Up9HVpMFRoSzfY1n+t8GF4/JroWYqxdrWJ1SuLAnOoflDfm4pV+hXX3puc/GrA4CdrPDQ==