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
- b51c55868dbb6f6968adca61addeb50f8d3dbc22df26a82cc9e0125fd7647d1a
- request
- 77927989908234fe3b24e9e4abd04169fe69e2fe336e74715d397f2808be459c
- transaction
- b7af6c4b8eb1385c93e0228c5a2e9f1e383cf7503c22cf1ee0b7c7280af11433computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66158
the chainentry 66158
- sealed to the entry before
- 3968ab7d3a137690d400c07fb638e866f024c76de1b8ef6f3ced8bff59fc2ff1
- this leaf
- 7dbbc6022d1c156306052c258178664fcd2ebec12ae9a6ac1a23f452f9785ed1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hd8sqJ8yj4vLbbN8IXrpyVRQFoNUyhRI2ai+9Ljke5IYuIfj4/90rt2k30PtKB9nhi4z0YYK6bUvrYoN7hi1Ag==