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
- 63fd415b6f6f4bc83d18bb2103e5018a83ceb88eec4fdf6b0555c7449829be36
- request
- 4a7691f0ee24e92f080a843ec4889384869b88d6c9fd9ddf1109ee179eab466d
- transaction
- 4bd7778bd75c9faffd0b02e8f7b5ab0d0ad49937ac6ca1c2f06463f451e37240computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44954
the chainentry 44954
- sealed to the entry before
- 1aa9f704ad682b0cead37a49777984207d7331dc6764001626eddd7c148f4776
- this leaf
- c7923171da70ae91641db3a2c8bd5955c0fc94c665f9ce4bc6aff68931b1f13d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- goDYdOKeaq5SYEf+CXQBHz+KECM5IeO0SyT80ShhiLf6E8Zpbk3tFhwVEi3kWxBDqIMJ/wB2Szso6qmT7JK2AQ==