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
- 0ffe25f980bb2b58789bfcb7ead82fd8f6aeb1eb3e016041215db575954db304
- request
- f00e4d06b435f14cfc4f2aa9ecaaa79ab490ab0734c8377f75031955d0e05d4d
- transaction
- cf8b78afda73642d54da629f12443ccb266ea34e4365bc7cf556032e2a4137a2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53097
the chainentry 53097
- sealed to the entry before
- e0529aa8cb605686f035db31585693bb07d65b70ce7020d58cc1dc4f07bc47cf
- this leaf
- 0bcbeefceba842c5573efc66115fdb05aff71093f07326da4ec5df7e0b194a6d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BQsmNG4dNqZfdB4T6aWlE23RsVzRmRcpBne+8DCjxm1dsl++wYHhvXBg9OQp4V+TK85zgsarXMc1dRZzc/4TCQ==