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
- 22655e0e3dc8395cdeba1c7e089cbc33bf8bda69cc70a2d8dd7f1871b6700a35
- request
- f0c244cf2b9c93d27845e20c6896434bf6d9154decca282bd74f7de431ff2584
- transaction
- cfd385c3ab06eef17c3e7045da6883fb74569b9a90c7aceb8b7c745a82c80ed1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68820
the chainentry 68820
- sealed to the entry before
- 288b30c15db061f0e57d648d8d2a86192233361046dd67a59ee7d56663e95bf8
- this leaf
- 3bf66904402a225d0c820d530a27fbebef353bce72a5a543bd85d8ef407ef8e7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JJhi8O44wnFELP0nwc97DcTtzGVaOMiIEqyKqkKMfTkwOJilTn7yk0DMCj3dQZublos9qYLXLVnzY/5C9SmpCw==