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
- 7d091fadda3944fecad6998d422cbfe8959615aa66d8b52db3798fafa7da957f
- request
- d2f396704ee8b34c0f828ff94e08610c90cf721de0973227d1eceeafbfbb1f5b
- transaction
- 90a9ecbc5dcdca149cffe8ccb99ae8881ae0d3a92008b3940a3b8cf2e4187bd4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36320
the chainentry 36320
- sealed to the entry before
- c2b1b03cd6abf940299404d42e76a6699e83e95d7084fdc192daca0002aa4ed6
- this leaf
- 38fa8b3bc21359610093cc92a9d6ea881bf23a32a7da82060e7c7bd8699c4f95
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gv8GVQzJUgUC6ipRS+dbxO4dduRShjOmdo8zGkaz5Gh7hqJhoMf8umbsJBfwnDpfKV1pdty4UHXUA6mgjRnyDA==