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
- 9d0a3ad86b34dc4191e627695727695a3edeb5025172b5f8de47312cbc104eca
- request
- 2d56cd9038f0d40538aba26d77a39e4364d8475d401d5b21dfeb5cbb6953c5ba
- transaction
- 431801e7b375d0910f05ce3afbfeee671fc0f3a8a01155ab954bc1e449c0555ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60959
the chainentry 60959
- sealed to the entry before
- 711cc8a459024ad8579d720ffbef549e3ab8cf23ca0448bb511a2513db850b20
- this leaf
- d8a1073204874ff66498c82eed1e21a324af52fdf98a6e51181872c35dee9a64
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Tp5+w5zSV3hzCuaqKUUqAOKWpqjy+hK1cY/sxIjaAVcD2OXEZCGJEGjG9cDMzys/Hwzp72WziD0PTr/qq8cBDw==