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
- 405cbbb83c54d4349173d8b0d49e9936ff17d79b149823d93e0dccb2f3733b6a
- request
- ba6ad0dea3e14889d4dac7db537b0fca175451643311500dfc4323e6c94f117d
- transaction
- f473b62dec086a849c33840a4d8d081ad5b228a2666855f7760c1aef0455ced2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74689
the chainentry 74689
- sealed to the entry before
- af97f9ae40cfcf69c968505efc9cc172617eaf019be71c644f71d96c0da0b495
- this leaf
- ef23d8989c19e7cb744a0a1f372baf57097f2a09ba83df3c26959058cba7c8b3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- c+EuEfSIEC06PXg3MNCuBj5yJy04oSbZAUG8zfbijKociSuiDG93n8khEKmvhBCFTvEVWwJvStAOGBgywhBbCg==