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
- c6f325fd60b8d9b8c604ec788bc22866734667ec48d3934ded952e4338aa92b0
- request
- 14973aa8e4b739d4fdcf79656fc718e834fec22fc667f8448ccdf2304ee2b3d0
- transaction
- 7ef84739bfe0ddd9d3c87e5f633d64b783e9004d42f0e1531fc107847317da5fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5342
the chainentry 5342
- sealed to the entry before
- 4f54160ffc4de8943b89dbbe1f8e8aec503b2874869fdcc031b8070361004981
- this leaf
- 4b167636316f41ea1d15dfb83a862929f46677f2f69609b00b46be83090eebfd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Jvrf+7cGSeZtyVFqumhvJ4klfW3tCs83eucOeJL+9UfAGyAd2Ik6b7khR08d5+4iMiytBR262PsL2uM0YfKlAw==