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
- d8e0385702d8855bc8f262b45534d1c263d77a592d7c21a5f0a3d2fffd34e268
- request
- 066c187dfb744b6caafe67f85cf9e27bd74f16cc26ffad0aecc73196a8fc2155
- transaction
- 3c071ef347be01bf25efc38f0226e00040c379159762fcc40f38ea8c6c11360ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48122
the chainentry 48122
- sealed to the entry before
- 784e5d5941a3376352abab6232eaea738c5bc01a6cf314276948ec6e6daa17e9
- this leaf
- 61bb6bdb20388e9489ae90d7ecc2d808859062a41ec6800160204901328fca0a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /JwvlFiqw5FzFJuv7xsaBBH1p1ENQiq+LDup9QVT8Ja09NRhK4mriIqyR/HUzCwBim496pQAw5U0XHMiZ0nxAA==