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
- 22bc6848b65da7b58a89668da825a944a4eb902716ce51c485a943173d589300
- request
- 8269beec962509ea6c8cd5506de99abd5e331d967e27e0ab24d8f3b06dacb304
- transaction
- 532a621f44a7d229e67d9b568ca515a1709474f079d2134637c7e5d621043416computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 186
the chainentry 186
- sealed to the entry before
- 0694677d513d75f9dfd9ce66840bfe64901ec66ff4a1b2509b517040cf4060fb
- this leaf
- cc51afffb5903ae21736e7de2927ddce5347d2f079158a3c6cdd42ae7ba78335
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oUwqhaXVC2LgAm5loIyaA9L8Qms7GqB7dgA/VRym3PbXeFsc383TjcwrC3Tol6yFroaKlJGCl14YBNINmfwaDQ==