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
- 3bfd2809232918277d303942f5a2dd6614d0833ecb1554f7a275b387b58cbfd5
- request
- 5ccacce54ab0d24160c7382e7a4719fb7c68fe35d1e781c05b7de71a467baec5
- transaction
- 9558bc8f97759703a09773ffb6bf01a2b12f4bc2a2aca45945d9b6614d9b1fddcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69746
the chainentry 69746
- sealed to the entry before
- 9b0162147885342960317b722d376f4834cd72a1f32564c3b607e47bd38bd707
- this leaf
- a62858d365c978f48c094829581b64d6df7afea2e5063c5af3e202455a72dd68
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- H/+Eg1aTHCbwJ2cbAowzKaa+sYUNxy9dbkMUV58L+1Ot1zl9aFgAxN2dgzAJfn/PxSxUb96mDbtox6s9KcqnBQ==