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
- 5da7ee7fc10faca64a0888396c9fc6b65d81e36f3182f05ef5795e3e17694ef6
- request
- 65695f29275e123d175fae27ff7be0bcef24a9c527567aeb97b0068ccf11ba2d
- transaction
- 237d23893477709f62d4e1498126f744e7078580a04ba5468567d4ee757b5dd6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24406
the chainentry 24406
- sealed to the entry before
- 9c558d0313f93e219566c31cafc3c3f993368fb157ef404f18f1e08cf485af8c
- this leaf
- d60b6386ab0df6c2dbbfbcbf7f93d27240d69c39661a27b4aa66616fd3c18dbf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /it59XvH658EOBxpcQcZoCSZYTE6adSxMV9P9dt9ojYac/TKua4qIhZTpzzDTEzI1dGO6JDVs3WLb+DprzUhCw==