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
- 3424da7be8584dd1161351c3eee6a02c57a44764e54217e2603d3909509575bf
- request
- d168532fe34ff03e55dfb8a2b5a290118d421f2087654082b58858649832d4bd
- transaction
- 8b6c6a65ed82bb53fee315cc5d4d44fe084522b164bddc62c085704175187314computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73310
the chainentry 73310
- sealed to the entry before
- b91d88ea9abaeb71ee61d725fff6fb3a64264238c78a567a8085fadeedeb0f96
- this leaf
- d54106f1b958ce30d12bf5beb3554347a037568039b8724911ee6c21bc945676
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gBoKDi5Bn4KXxH59dYfK/iqEHCmqgDCjfmA88c2QaanIueJo53gSR4d4vmcDCn0Wa5F/svf3pLwo63KvH4VFBg==