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
- e8aabecdbd47be05c43da79a5a8609eeb447df1886ba1026baaf3756283df6e9
- request
- 1fc12b62a3df47538f1b4f5a25387c85bed9cd996c4bf230066bb23b049c534c
- transaction
- 89d26e863295ad4040c5cdcb2d164024bbebab55b7bdf1c2d24482fc19e8aff5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47491
the chainentry 47491
- sealed to the entry before
- 3552f33195c7528e6e0973df1709d2fbb32ff43bf3da0b1f04da2cbed9558117
- this leaf
- b37d46c2fb8254ae2640bf93c4de1894c9176abf60bce57a7bf8cffcd92c36a8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- q09RrXQpT/emAeNmEbNgojdvjGUBzEEUxJLP3S8cZnvWa/3lWj3ueg3e175u3tdmGjYSh77n7lpsqN4VuK5vDA==