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
- ddfe7e18022cb6c2e53e2b3b77929a34c9f4497d37c3b1e82421720a642cf94c
- request
- 4689c0b1a4b0489f3b9298371633d666a3dd59a83be10b90d474d41733568037
- transaction
- 4d5af5eba7e1626afb5b0889a3685411c43ff45974a11dccee4c8a384a2f15bfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45002
the chainentry 45002
- sealed to the entry before
- ba41aa963769cc320d0438e50429ee43c154cf98b2f969534affb2e14bc4d82e
- this leaf
- 225a48995390e88fe9b6da89f4222da47708cd3054e5102e9db36a1c4b6281d1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PUkFZz89Gyt2eA9R0pBwbc4zToQ4et/HewuZRdY7BziyQUTkPI5GvsfZjSi2LKncNB1HJD7LU9MidR3lt49FDA==