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
- ef75a5a996efbe771213f9ea75bf1fc99b2ba11f207eccee43760f854188e146
- request
- ffe0a12a059480d5ba5173d50e673b58f468eedc0d964d7ecabcd5a103dd27f4
- transaction
- 08b8b2278376ede033c5f7d8b0c5828bc8cbf8dc0ecf44a9119c4f37e16cc10bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30861
the chainentry 30861
- sealed to the entry before
- 8f75761e53c85cf315a82805bf08f62d1bc86aeaa92f29413b3eda4f53e4e3da
- this leaf
- ecb714f901815d9154fdb9189886b1df2ef5dc3ac884c7447a6166c16fdd6231
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7KWUSnXDIiIkp2Fdqf+8TmpHAj1VgA85eRD5ou5Wh9n3DibcyHnNC6IJoI3oPbVMkBloE1u12mPHJrNeoJTFDA==