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
- bfde0f9f999610d86741a026f9ee5a698646c93d6836bedf4cfc254460511115
- request
- ef14e4d883920130b8eff275368f077fe78fc096c7752d88193347e6f835c050
- transaction
- aa33038b0919821872cb2b91ef1a5545691a7e797561a1c6c03c37e10fdbf27dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5033
the chainentry 5033
- sealed to the entry before
- 661fc032213dcbedcab0056c8b2c7591469ebd989fe196197f03ca6e19714052
- this leaf
- d574695d70e55db6f51b0be5b538e0c76eeabc6705bac1a69ef6f3a3c2e76fb5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 09DeRzane7xXRIIrLddiUwf1yNNzuc+pTsSHuYkjDtN2tv6LNumt5eE+tmKHIjaIrT3OJwWk8CkrcRX+Coh5AQ==