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
- d8f1ee267660334f2311bc37baf70653a6fac6d582e71403d86a1083580e12aa
- request
- 3280c7eb0b78f4b2901eed9b69c746275055c5aa327e5ee69fa51c0f5a1731f9
- transaction
- 7f96476a56627b0fd05d4e84ad3ce9dcc251e7dcbaa028d2b9205261576eaf70computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49428
the chainentry 49428
- sealed to the entry before
- e52c1174a8664ffea56db71b9d536c147ca9b9b7e6f83acd59f602ec331b521b
- this leaf
- 10ab6a4a5e9c11ee502112a747809573d1ac6e08a72e1a3828a39f9066942e8c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2ycteCK9nuBdltGcK91zCuo8r+MKoEx/B65eBGLw60nkmKsJudk8U8Vx443AyhYfNnPeGwdMJzYIE3K5+YZyBw==