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
- a73cebc80fe51dfb0eba2035fae0e69bb765c71a44b0f44cc85a759139420999
- request
- daf33fcae01dc704177aa16452380813010a77dd32ddfb7e5ea82b80c8787386
- transaction
- 3eafbd30f279f17b2213a00ef2769c2069969263f7e45c65ff8500b82c3353e0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73326
the chainentry 73326
- sealed to the entry before
- a5828eaa99f6441f529760613a272be5d8c2f15c1cd8ac664bb85d49adcf1381
- this leaf
- 03c111265703e05a7716adcb81a611adf1ac9a5537ea8f1ccbb530c7c121a8b9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- x33ZUEXll/5dAv1V5WQKrnlwpbusqnN2MLWkAUvyE0F/e7MHXwae/DpRJSmgxUzxasoRpKEJCNYpc2Wn5gQ/Dg==