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
- 5d30880408ca55a626e257ea18c6b5afe7c6d256aa0dd96f76d1105088e1bdde
- request
- 7c302bba7b54f37031de1c2594a1c6d0b136d2632fed98de8257793b4c856398
- transaction
- edfe52059139420d07dcc305c56180c412bdbd8e5de2605f66c3bc79c8e9c3fccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63123
the chainentry 63123
- sealed to the entry before
- 7961a040eaa14cffb3403c4a0f373e9f806add83a45c85677927b2a549354648
- this leaf
- ee317533be85259552c63903f5de42591f977966c2250e4aed9a0b9b15ad7826
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zxvhihg+iEU1/8TbQTkioRX6dTZNv0+yzYs8eAwoKOzeGbA920ngeSOGmOFdYP5d//f85B/5PITe98eGSZlMDQ==