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
- e901db65756a4d27e1624fc1b3c22c9413745391cdb857e89c949311c2a37ccc
- request
- 75f51732dffc71614672f36b0d30f8f12fe747f9e4b79efe6538c574203e0bb6
- transaction
- 8949f5a4c1672b83a1485ce8a784aeeadcd95d576564adf578d72b32fc353694computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77621
the chainentry 77621
- sealed to the entry before
- b515a630d103365ef8593062ec42ccd1a73de172700d2c3e99b0b82be4b31381
- this leaf
- df032c64ee516e563ba42d483ab3f55699ba72a07f0dc1c77cd89500fcb9c96f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nK/niqEzUmrnj6WL96/45HSWbA0QcFFEtCzQ5rvLEsQOQPC+28nBpzidBvi/iNJ12Rnl15oCj4zv/pJDzVB0Cg==