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
- 3c04925828ed372a1233d5a1675affeaaf8580c60e28be7d5dc00fd5965ab8d9
- request
- 3ecb33569cb3394f228fe3d31bffd80525d2a838eb638ca4d0fda13bf70da105
- transaction
- 6c780d42cb31ba0ebd6f9886edfc080171b517447cb2a796991a6dc837a4354fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22450
the chainentry 22450
- sealed to the entry before
- 17c578f32a531ae1b9402954568a92eec42363f9dda031fb56df402503417e83
- this leaf
- 72a4771d42b61584e87bda97fea45a6a5a9d52a3bf8191680be14ffd5b6afc11
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ItxT48M4R1fTbLD0rANPhnB5tvWxMFEPMIPBvB/TmHKGrxuHi/uuzvL42QY0FoPfMQzlMbLeaB67SJ3RtR8aBg==